Skip to content

ci: Build releases from the full tag ref and pin cargo-edit - #590

Open
ebma wants to merge 2 commits into
mainfrom
ci/release-checkout
Open

ebma wants to merge 2 commits into
mainfrom
ci/release-checkout

Conversation

@ebma

@ebma ebma commented Oct 27, 2026

Copy link
Copy Markdown
Member

What changes

  • release.yml
    • Checks out the pushed tag as refs/tags/<tag> and confirms that HEAD is the tagged commit before building. A short name lets actions/checkout resolve a branch of the same name first.
    • Tests ancestry against refs/remotes/origin/main.
  • version-up.yml
    • Installs cargo-edit 0.13.13 with --locked before the checkout, so every run builds the same dependency tree.
    • The checkout no longer persists the token. The step that creates the release branch receives it and creates the branch through the API, like the steps that commit to it.

Testing

  • actionlint on both workflows.

ebma added 2 commits October 27, 2026 12:03
The release build checked out the pushed tag by its short name, and
actions/checkout resolves a short name to a branch before a tag, so a
branch named like the tag would be built in its place. Check out
refs/tags/<tag>, confirm that HEAD is the tagged commit before building,
and test ancestry against refs/remotes/origin/main so that a tag named
origin/main cannot stand in for the branch.
Install cargo-edit 0.13.13 with --locked before the checkout, so every
run builds the same dependency tree and no repository credentials are
on disk while it builds. The checkout no longer persists the token; the
step that creates the release branch receives it and creates the branch
through the API, like the steps that commit to it.
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