CI-hardening mini-WP: upload regenerated artifacts on gate failure (if: always())#18
Merged
Merged
Conversation
…ails CI-hardening mini-WP item (spec v5 section 6, parallel-allowed after WP10). The job still fails on gate drift; if: always() on the upload step preserves the regenerated bytes so an R15 re-baselining PR can adopt CI's output as the committed reference (no local C++ toolchain exists on the dev machine). The reproducibility gate remains the single authority. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Small CI-hardening item, explicitly allowed to run in parallel after WP10 (spec v5 section 6, CI-hardening mini-WP).
The reproducibility gate stays the single authority and still fails the job on any drift. This change only adds
if: always()to the artifact-upload step so that when a legitimate, R15-documented pin change regenerates different bytes, the CI-regenerated artifacts are preserved and can be adopted as the committed reference - required because the dev machine has no C++ toolchain (CI is the verification reference since WP5).No behavior change to build/test/gate. Needed by the upcoming WP11 re-baselining (abort-law change moves campaign rates under the full R15 protocol).
?? Generated with Claude Code