Skip to content

refactor: vendor legacy contract artifacts, fold compat e2e into the norm… - #25163

Draft
mverzilli wants to merge 1 commit into
merge-train/fairies-v5from
martin/compat-vendored-artifacts
Draft

refactor: vendor legacy contract artifacts, fold compat e2e into the norm…#25163
mverzilli wants to merge 1 commit into
merge-train/fairies-v5from
martin/compat-vendored-artifacts

Conversation

@mverzilli

Copy link
Copy Markdown
Contributor

(wip)

…al suite

Commit the historical contract artifacts (one tarball per prior stable
release) under yarn-project/end-to-end/legacy-contracts/, and emit the
backwards-compat sweep from the normal e2e test_cmds under CI_FULL. The
jest resolver unpacks the committed tarballs on demand — no npm at test
time — and because the artifacts now live in the tree, the build content
hash keys every cache correctly with no special-casing.

This deletes the compat concept from workflows and CI files entirely:
release_compat_e2e, compat_test_cmds, SKIP_COMPAT_E2E, and the
ci-skip-compat-e2e label handling are gone. The only remnant is
check_compat_artifacts_tracked in ci-release, which refuses to cut a
release while a prior stable's artifacts are missing from the tree.

Full-mode AWS_SHUTDOWN_TIME goes to 90 since full runs now include the
sweep.
@AztecBot AztecBot added the port-to-next Forward-port this merged PR into next label Aug 10, 2026
@mverzilli mverzilli added ci-draft Run CI on draft PRs. and removed port-to-next Forward-port this merged PR into next labels Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-draft Run CI on draft PRs.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants