Repository navigation
ci: guard dependency pins against cross-workflow drift - #16
Merged
Merged
Conversation
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
1 participant
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
Taskly currently pins Rivet/Keel in multiple independent places across
ci.yml,acceptance.yml, andrelease.yml. The workflows are internally DRY, but there is no repository-level guard keeping those pins aligned.This adds a lightweight contract preflight that:
RIVET_PINvalues to matchsetup-embed-racket@<sha>ref matches that Rivet pinacceptance.yml'sKEEL_PINThis is intentionally a drift detector rather than a YAML indirection layer, because GitHub Actions does not allow dynamic expressions in
uses: ...@ref.Why
A Rivet bump currently requires coordinated edits across build, product-acceptance, release, and composite-action refs. A partial bump can produce the worst kind of failure: CI passes with one framework revision while packaging or acceptance executes another.
Validation
The branch is two commits ahead of
mainand only changes the contract workflow plus the new preflight script.