Skip to content

Send the package owner organization on publish - #1307

Merged
ericmj merged 3 commits into
mainfrom
publish-owner
Nov 6, 2026
Merged

ericmj merged 3 commits into
mainfrom
publish-owner

Conversation

@ericmj

@ericmj ericmj commented Nov 6, 2026 •

Copy link
Copy Markdown
Member

When you publish a new public package with mix hex.publish and 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 --wait was still running then.

The chosen organization is now sent as the owner parameter 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.

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.
@ericmj
ericmj merged commit 2e203ef into main Nov 6, 2026
15 checks passed
@ericmj
ericmj deleted the publish-owner branch November 6, 2026 13:31
@ericmj ericmj mentioned this pull request Nov 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant