chore: add 5.2.0 legacy compat artifact - #25250
Merged
Merged
Conversation
nchamo
marked this pull request as ready for review
August 17, 2026 17:34
mverzilli
approved these changes
Aug 17, 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.
Summary
v5.2.0), socheck_compat_artifacts_trackedinbootstrap.sh(added in refactor: run compat tests on committed legacy artifacts #25163) now fails every full CI run on v5-next with "stable release(s) missing committed compat artifacts: 5.2.0" — including all merge-queue candidates, which currently cannot land.yarn-project/end-to-end/legacy-contracts/5.2.0.tar.gz, generated withadd_version.sh 5.2.0from the published 5.2.0 npm packages (deterministic, byte-reproducible), as the check's error message instructs. This enables the backwards-compat e2e sweep for 5.2.0 and unblocks the v5-next merge queue.