Fix the private hex publish step - #24
Merged
Merged
Conversation
The step configuring the flickswitch repo passed --api-url to mix hex.repo add, which Hex does not accept, so the job failed before either publish ran. The private publish itself then passed --repo to mix hex.publish, which Hex also does not accept. The registry is our vendored mini_repo, which takes a publish over its own HTTP API. Point Hex at that API with HEX_API_URL instead, scoped to the step so the hex.pm publish keeps the default. mix hex.repo add configures reads only and is not needed to publish, so drop it. Publish the package without docs: mini_repo serves packages only. README documented version 0.1.0 and no private repo. Document both consumption paths and how a release is cut. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
v1.1.2 came out as a draft release. Consumers fetch the precompiled NIFs from the release assets, and an anonymous mix deps.get cannot read a draft, so every consumer without a local build would fall back to compiling Rust from source. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
louisvisser
changed the title
louisvisser
marked this pull request as ready for review
September 3, 2026 10:48
louisvisser
requested review from
Tom-Wyszkowski,
avenderossa and
pringlewood
September 3, 2026 10:48
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
2 participants
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.
The dual-publish step added in #22 never worked: it passed flags to
mix hex.repo addandmix hex.publishthat Hex does not accept, so v1.1.2 failed before publishing to either hex.pm or the private repo.Our registry is a vendored mini_repo, which takes a publish over its own HTTP API rather than through a repo-scoped flag. The private publish now points Hex's API URL at it, scoped to that one step so the hex.pm publish above is untouched. Registering the repo, which only ever configured reads, is gone.
The README still advertised version 0.1.0 and no private repo at all, so it now covers both ways to consume the package and how a release gets cut.
🤖 Generated with Claude Code