Repository navigation
chore(next): track aztec nightlies (6.1.0-nightly.20261025) - #71
Merged
Merged
Conversation
The latest nightly was picked by filtering versions on a hardcoded `6.` major, so the moment nightlies moved to a new major the script would silently keep updating to the old one. Read `dist-tags.nightly` instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
v6.0.0 is on main now, so next goes back to tracking the nightlies. @aztec-foundation/* resolves to 6.0.0-rc.7, which is what the 6.1.0-nightly.20261025 @aztec-labs packages pin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The header said "v5 (main) and v6 (next)", which went stale as soon as v6 landed on main. Describe the split by role instead: main follows the latest Aztec release, next the nightlies. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
🚀 Web wallet deployed! Preview URL: https://demo-wallet-next-ckt3r0x4j-thunkars-projects.vercel.app |
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.
v6.0.0 is on main now (#70), so
nextgoes back to the nightlies.@aztec-labs/*dep to6.1.0-nightly.20261025.@aztec-foundation/*resolves to6.0.0-rc.7, which is what those nightly packages pin, even though stable 6.0.0 uses foundation6.0.0.update.jsnow picks the latest nightly from npm'snightlydist-tag, not by filtering on a hardcoded6.major, so a future major's nightlies get picked up automatically.Lint, typecheck and tests pass locally.
Open question:
testnet(the default network) still points at the v6 testnet (testnet-v6.rpc2.aztec-labs.com) with auto-detected rollup version. A 6.1 nightly SDK may not stay protocol-compatible with the stable v6 rollup, sodemo-wallet-nextmay need its own nightly/staging network at some point.Not included: the
deploy-web.ymlheader comment still says "v5 (main) and v6 (next)". It should now say stable (main) vs nightlies (next), but my token can't push workflow changes.🤖 Generated with Claude Code