Repository navigation
Send the package owner organization on publish - #1307
Merged
Merged
Conversation
mix hex.publish published a new package with the user as owner and then transferred it to the organization chosen at the owner prompt in a second request. When that request failed the package stayed the user's, and a staged release was only transferred if --wait was still running at approval. The chosen organization is now sent as the owner parameter of the publish request, and hex.pm creates the package owned by it. Vendors hex_core with the owner publish parameter. Integration CI runs against the hexpm publish-owner branch until that change merges.
This was referenced Nov 6, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When you publish a new public package with
mix hex.publishand are a member of an organization, Hex asks whether you or one of your organizations should own it. If you picked an organization, Hex published the package with you as owner and then sent a second request to transfer it. If that request failed, the package stayed yours. With staged publishing the package doesn't exist until approval, so the transfer only happened if--waitwas still running then.The chosen organization is now sent as the
ownerparameter of the publish request, and hex.pm creates the package owned by it (hexpm/hexpm#2110). This removes the client-side transfer and its "Ownership can be transferred to ORG after approval" message. hex_core is vendored at 10707bf, the merge of hexpm/hex_core#260.hexpm ignores query parameters it doesn't know, so against a hexpm without hexpm/hexpm#2110 the package is published owned by you and nothing transfers it. hex.pm has to be deployed with that PR before a Hex release includes this one.