Conversation
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.
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
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.
Summary
releases/latest/download/casacwithreleases/download/${CASAC_RELEASE_TAG}/casacenvso future bumps touch one line per workflowWhy
releases/latestis a moving target. Any PR that introduces new syntax to the compiler orlib/std.casabefore that syntax exists inmainwould 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
vX.Y.ZfrommainCASAC_RELEASE_TAGin both workflowsTest plan
v1.9.0binary