fix: bind Evals releases to exact CI and notices - #339
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
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.
PR #338 could not safely merge because the tag job did not check CI for the post-merge
mainSHA, and the archives omitted VAGEN's required MIT notice. This fixes both release boundaries before the bot proposes 0.97.0 again.The release job now queries the
test.ymlpush runs for the requested 40-charactermainSHA. It refuses missing, pending, failed, cancelled, timed-out, API-error, and SHA-mismatched evidence before it creates a release App token. A dispatch made before the exact push run completes must be tried again.The wheel contains modified copies of two VAGEN abstract environment files.
NOTICErecords the source repository, commit, paths, upstream and distributed SHA-256 values, modification state, and the full upstream MIT notice. Both pull-request CI and the release job inspect the built wheel and sdist. A changed vendored file, missing notice, or changed archive notice now fails.Verification:
The copied files first entered at
c7845ff. Tagged v0.25.0 and later releases contain that commit. This pull request stops the notice omission in the next release. Audit the historical PyPI files and make any yank decision only after a compliant replacement is live.Opened by an agent session, not the founder.