Fix make release failing with "Command hex not found" - #190
Merged
Merged
Conversation
`rebar3 hex build` and `rebar3 hex publish` come from the rebar3_hex plugin, which was never declared anywhere, so releasing failed as soon as it reached the publish step. Add rebar3_hex to project_plugins. Also move `git tag` to after `rebar3 hex publish`. Tagging first meant a failed publish left a stray local tag behind, which then blocked the retry because the tag already existed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Releasing broke at the publish step with
===> Command hex not found.What changed
rebar3_hextoproject_pluginsinrebar.config. Thehex buildandhex publishtasks come from that plugin, which was never declared in the project or in the global rebar3 config, somake releasecould never reach Hex.rebar3 help hexnow lists the build/publish tasks.git tagto afterrebar3 hex publishin thereleasetarget. Tagging first meant a failed publish left a stray local tag behind, which then blocked the retry because the tag already existed.For the reviewer
.tool-versionswas not the right place for this. It pins tool versions (erlang, elixir, rebar), not rebar3 plugins.Anyone who hit the old ordering may have a stray unpushed tag locally.
git tag -d <tag>clears it.🤖 Generated with Claude Code