Skip to content

docs: rebuild a tag by hand only while main holds its version - #103

Merged
rubas-agent[bot] merged 1 commit into
mainfrom
rebuild-main-version
Nov 14, 2026
Merged

rubas-agent[bot] merged 1 commit into
mainfrom
rebuild-main-version

Conversation

@rubas-agent

@rubas-agent rubas-agent Bot commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

Before

RELEASE.md, "Manual / out-of-band release":

It replaces the existing release artefacts. Then follow steps 3 and 4 above.

Problem

Steps 3 and 4 take the version from main. task checksum:download downloads the tarballs of the @version of the checkout, and release.yml:detect reads mix.exs of the pushed commit. Say an owner rebuilds an unpublished v0.5.0 while main holds 0.7.0: step 3 writes the 0.7.0 checksums, and the merge in step 4 publishes v0.7.0 or nothing. The rebuilt v0.5.0 can't reach Hex this way.

After

It replaces the existing release artefacts. Then follow steps 3 and 4 above while @version in mix.exs on main still names the tag, because both steps take the version from main. Otherwise release a new patch version instead.

Details

#98 kept a condition here: follow steps 3 and 4 only while lib/, native/, and mix.exs on main still equal the tag. #101 moved the publish job to the sources of the tag and dropped the condition, but the version still comes from main (release.yml:detect, git show "$SHA:mix.exs"). This PR brings back the part of the condition that still holds. Docs only, so no test.

The checksum task and the publish job take the version from main, so steps
3 and 4 cannot publish the rebuilt tag of an older version.
@rubas-agent
rubas-agent Bot merged commit a83ffd5 into main Nov 14, 2026
1 check passed
@rubas-agent
rubas-agent Bot deleted the rebuild-main-version branch November 14, 2026 08:49
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