Repository navigation
chore(release): prepare v4.21.0 with self-hosted qualification - #336
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
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.
Prepare
aether-agentsv4.21.0 from the changes since v4.20.0.Local evidence: production verifier passed (1,052 packed files), release truth 12/12, generated docs check, npm audit with 0 vulnerabilities, targeted regression tests, and installed-tarball 401 recovery. The first full local run had 3 failures; two were stale assertions and one needed Python 3.12 set explicitly. Their targeted rerun passed.
PR #336 uses job-log evidence while Actions artifact storage is at quota. The private ATSv2 checkout is unavailable to these runners, so cross-repository parity is recorded as unavailable; independent ATS contract tests remain active. All ordinary CI upload and parity gates remain in place.
The npm registry still serves 4.20.0. Self-hosted publication will have no npm trusted-publishing provenance and requires an authenticated npm maintainer. This PR does not publish npm.