Refresh pinned evidence toolchain - #6
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
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.
Outcome
Refresh SensorProof's pinned evidence-only toolchain while preserving the released behavior and independently regenerating the complete evidence bundle.
Updates
actions/setup-python6.3.0 → 7.0.0 at full SHA5fda3b95a4ea91299a34e894583c3862153e4b97;greenlet3.2.4 → 3.5.4;pyee13.0.0 → 13.0.1;typing-extensions4.15.0 → 4.16.0;provenance-toolchainDependabot PR.This supersedes Dependabot PRs #2, #3, #4, and #5 without adding bot-authored commits to project history.
Evidence refresh
The one-shot branch workflow:
All 12 payload evidence files remained byte-identical. Only
sensorproof-evidence.jsonchanged, updating its source revision/tree binding and source hashes.Commit contract