Repository navigation
ci: replay workflow hardening after develop-path merge - #421
Merged
Merged
Conversation
the1mills
approved these changes
Sep 16, 2026
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.
Semantic current-main successor to #416, rebuilt from
main@bbd24936796bb19231299f69a19cf4152f8da5dbafter #415 advanced the base and made the prior carrier non-mergeable.This replays only the six reviewed hardening changes from #416:
gh auth setup-git;sys.modulesbefore execution.No product source, manifest, Cargo lockfile, generated contract, release metadata, or FP budget was replayed. Exact-head executed failures remain blockers; genuinely runnerless/zero-step Actions caused by unavailable build minutes may be treated as unavailable evidence per the current merge policy.