You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prepare the requested 6.0.0-rc.7 npm prerelease so the tag-driven Release workflow can exercise the stable Aztec v6 build and publishing path.
What changed: set the package version to 6.0.0-rc.7. Aztec dependencies, Noir pins, and config.aztecVersion remain on stable 6.0.0 from PR #62.
Breaking changes: none beyond those already included in the merged v6 update.
Not in this PR: tag creation and npm publication. After merge, create v6.0.0-rc.7 at the merge commit to trigger Release; approve the existing Production gate after inspecting its built tarball. The workflow publishes under npm's rc dist-tag and smoke-tests the published package. The separate Pre-Release dispatch workflow produces a SHA-suffixed GitHub tarball, not this version. This session has no tag-creation or workflow-dispatch tool.
Validation: yarn build and git diff --check pass; the generated manifest has version 6.0.0-rc.7 and Aztec version 6.0.0. yarn lint-staged reports no applicable files. The pre-commit hook's unconditional Noir formatter could not run because aztec-nargo is unavailable, so the hook was bypassed for this package.json-only commit. Full validation is left to PR CI; npm publication remains unverified.
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
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.
Prepare the requested 6.0.0-rc.7 npm prerelease so the tag-driven Release workflow can exercise the stable Aztec v6 build and publishing path.
What changed: set the package version to
6.0.0-rc.7. Aztec dependencies, Noir pins, andconfig.aztecVersionremain on stable6.0.0from PR #62.Breaking changes: none beyond those already included in the merged v6 update.
Not in this PR: tag creation and npm publication. After merge, create
v6.0.0-rc.7at the merge commit to trigger Release; approve the existing Production gate after inspecting its built tarball. The workflow publishes under npm'srcdist-tag and smoke-tests the published package. The separate Pre-Release dispatch workflow produces a SHA-suffixed GitHub tarball, not this version. This session has no tag-creation or workflow-dispatch tool.Validation:
yarn buildandgit diff --checkpass; the generated manifest has version6.0.0-rc.7and Aztec version6.0.0.yarn lint-stagedreports no applicable files. The pre-commit hook's unconditional Noir formatter could not run becauseaztec-nargois unavailable, so the hook was bypassed for this package.json-only commit. Full validation is left to PR CI; npm publication remains unverified.Created by claudebox · group:
slackbot· requested by ilyas · Slack thread