Skip to content

fix(release): check out the tag, never a branch of the same name - #9

Merged
sanskarIN merged 1 commit into
mainfrom
v1.0.0-fixed-web-version
Sep 26, 2026
Merged

sanskarIN merged 1 commit into
mainfrom
v1.0.0-fixed-web-version

Conversation

@sanskarIN

Copy link
Copy Markdown
Owner

The build jobs checked out the release by its short name. actions/checkout prefers a branch over a tag with the same name, so with a v1.0.0 branch in the repository the release would have built that branch instead of the tagged commit. Every checkout now uses the full refs/tags/ reference.

What this changes

Why

How it was tested

Checklist

  • cargo fmt --all --check, cargo clippy --workspace --all-targets --locked -- -D warnings, and cargo test --workspace --locked pass
  • For web changes: npm run format:check, npm run typecheck, and npm test pass
  • New or changed findings carry evidence, a method, and limitations, and have tests with realistic samples
  • No network access, telemetry, or execution of repository code was added to the analysis
  • Documentation in docs/ is updated, and user-visible changes are listed under "Unreleased" in CHANGELOG.md

The build jobs checked out the release by its short name. actions/checkout prefers a
branch over a tag with the same name, so with a v1.0.0 branch in the repository the
release would have built that branch instead of the tagged commit. Every checkout now uses
the full refs/tags/ reference.
@sanskarIN
sanskarIN merged commit 35e0235 into main Sep 26, 2026
44 checks passed
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