chore: remove unused l1-contracts repo mirror from release flow - #24929
Merged
mverzilli merged 5 commits intoJul 24, 2026
Merged
Conversation
Stop pushing release tags to the AztecProtocol/l1-contracts mirror; the @aztec/l1-artifacts npm package is the supported distribution channel. The public and private release flows now share the same l1-contracts release entrypoint (the npm publish). To cover the mirror's remaining consumers: - expose the bundled foundry subtree via package exports - ship the governance payload contracts the rollup-upgrade tutorial deploys (RegisterNewRollupVersionPayload, TestPayloads) - point the tutorials at @aztec/l1-artifacts instead of the mirror
mverzilli
commented
Jul 23, 2026
fcarreiro
approved these changes
Jul 23, 2026
charlielye
approved these changes
Jul 23, 2026
…sumption RegisterNewRollupVersionPayload ships in src/periphery, which the @aztec/l1-artifacts bundle already contains (verified against the published 5.0.1 tarball), so the rollup-upgrade tutorial deploys it from there and the bundle only needs the test-only EmptyPayload grafted in. Also documents how Foundry and Hardhat projects consume the npm package (forge install cannot fetch it: it only clones whole git repos, and the sources include generated files that exist only in built distributions).
…l network Walked the full tutorial on a running 5.0.1 local network using the published @aztec/l1-artifacts bundle: deploy, payload, propose, vote, execute, and canonical-rollup verification all pass. Two fixes from the run: AZTEC_PROVING_COST_PER_MANA=0 reverts the deployment with FeeLib__ProvingCostBelowFloor (the local network deploys with 100), and the deploy script already emits payloadAddress, so Step 5 is optional.
mverzilli
commented
Jul 23, 2026
mverzilli
enabled auto-merge (squash)
July 24, 2026 11:15
rangozd
pushed a commit
to rangozd/aztec-packages
that referenced
this pull request
Aug 5, 2026
BEGIN_COMMIT_OVERRIDE chore(port): forward-port remaining v5-next fairies backlog to next (AztecProtocol#24949) chore: remove unused l1-contracts repo mirror from release flow (AztecProtocol#24929) chore: merge next into merge-train/fairies (resolve conflicts, unblock AztecProtocol#24951) (AztecProtocol#24965) chore: merge next into merge-train/fairies (resolve conflicts, unblock AztecProtocol#24951) (AztecProtocol#24967) END_COMMIT_OVERRIDE
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
3 participants
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.
Stop pushing release tags to the AztecProtocol/l1-contracts mirror; the @aztec/l1-artifacts npm package is the supported distribution channel.
The public and private release flows now share the same l1-contracts release entrypoint (the npm publish).
To cover the mirror's remaining consumers: