Repository navigation
Fix nested tooling pin for signed release preparation - #281
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
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.
Cause
Signed release run 42515351965 passed its preflights but failed before creating assets. The signing job omitted the existing pioarduino constraint, allowing nested Core 6.2.0.post1 to replace SCons during the build and fail importing SCons.Tool.FortranCommon.
Fix
Reuse the same job-level UV_CONSTRAINT as the successful nightly/custom jobs, plus a focused release-workflow regression assertion. No dependency upgrade, firmware behavior, signing policy, or security-setting change.
Validation And Release Identity
Focused release-workflow contract and raw whitespace checks passed locally. Require independent reviewer-agent review and relevant CI before merge. The immutable v3.1.16 tag stays at 8e21742. After merge, dispatch a new preparation run from main against that unchanged candidate and v3.1.15 previous stable, bootstrap_catalog=false. Evidence will distinguish workflow SHA from firmware candidate. The failed run created no draft assets and no scale was flashed.