Repository navigation
Conversation
|
🚀 Deployed to Vercel! Bridge: https://aztec-kit-bridge-next-f8n5bxbta-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.
Nightly bump of
nextto6.1.0-nightly.20261029(@aztec-labs/*,.aztecrc, Nargo.toml tags,yarn.lock) vianode scripts/update.js.Triggered by the nightly tag run: AztecProtocol/aztec-packages Nightly Release Tag #610 (aztec-packages
next@e4d9fee).Local verification
yarn format:fix: no changesyarn build: 7/7 tasks greenyarn test: 11/11 tasks green (swap 4, embedded-wallet 11, contracts-aztec 29 unit tests; e2e playwright 10 passed againstaztec start --local-network)No migration fixes were needed.
Notes
6.1.0-nightly.20261029installer requires Node ≥ 26.12.0. Repo CI already pins26.12in.github/actions/setup/action.yml. Only the bump container (Node 24) needed a local Node 26.12 install.bcryptofails inside the repo's hoistedundici(InvalidArgumentError: invalid onError method). Locally I worked around it withnpm_config_nodedirpointing at the Node install. If CI hits the same error when buildingbcrypto, that's the cause.Created by claudebox · group:
aztec-kit-nightly· Slack thread