Repository navigation
ci: pin rivet to v0.12.0 - #23
Merged
Merged
Conversation
turinglambdaai
force-pushed
the
chore/rivet-v0.12.0
branch
from
October 19, 2026 11:24
628ac96 to
bfdf71a
Compare
Closed
The dependency pin preflight requires full 40-hex SHAs (immutable trust chain), so the pin records the release commit instead of the tag name.
turinglambdaai
force-pushed
the
chore/rivet-v0.12.0
branch
from
October 19, 2026 13:19
bfdf71a to
e008c98
Compare
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.
Superseded by #25, which reapplies the same Rivet v0.12.0 pin on top of the current main after the updater fixes. The v0.12.0 annotated tag was verified to dereference to
1ebb3ac09ed2e23eeb0a91cbec6e689aac01ab1a.