Skip to content

ci: pin casac release binary to v1.9.0#160

Merged
frendsick merged 1 commit intomainfrom
ci/pin-release-tag
Apr 28, 2026
Merged

ci: pin casac release binary to v1.9.0#160
frendsick merged 1 commit intomainfrom
ci/pin-release-tag

Conversation

@frendsick
Copy link
Copy Markdown
Owner

@frendsick frendsick commented Apr 28, 2026

Summary

  • Replace releases/latest/download/casac with releases/download/${CASAC_RELEASE_TAG}/casac
  • Hold the tag in a job-level env so future bumps touch one line per workflow

Why

releases/latest is a moving target. Any PR that introduces new syntax to the compiler or lib/std.casa before that syntax exists in main would either need a transitional release (just shipped one for #159) or be blocked. Pinning the tag decouples branch CI from release-channel drift.

Workflow on next release

  1. Cut release vX.Y.Z from main
  2. Same/follow-up PR bumps CASAC_RELEASE_TAG in both workflows

Test plan

  • Both checks green on this PR using v1.9.0 binary

Replace the floating `releases/latest` URL with an explicit tag held
in `CASAC_RELEASE_TAG`. The pin is bumped in the same PR that ships a
new release, so CI never silently picks up a binary the branch has not
been validated against and stays immune to syntax-introducing PRs that
out-pace main.
@frendsick frendsick merged commit ea7937f into main Apr 28, 2026
2 checks passed
@frendsick frendsick deleted the ci/pin-release-tag branch April 28, 2026 20:12
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