chore: upgrade to Aztec v4.2.0-aztecnr-rc.2 - #12
Merged
Conversation
Update all version references from v4.1.0-rc.2 to v4.2.0-aztecnr-rc.2 and fix code snippets verified against the actual GitHub source at that tag. Version bump across config, docs, and scaffold (9 files). Syntax fixes verified against GitHub (4 files): - GENERATOR_INDEX__NOTE_HASH → DOM_SEP__NOTE_HASH (data-types.md) - Remove explicit owner/randomness from #[note] struct examples (notes.md) - UintNote::new() → struct literal, U128 → u128 (notes.md) - self.emit(note, ...) → .insert().deliver_to() (notes.md) - .call(&mut context) → self.call(), fix arity (partial-notes.md) - .call(self.context) → self.call() (transaction-lifecycle.md) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
v4.1.0-rc.2tov4.2.0-aztecnr-rc.2across 9 files (config, docs, scaffold deps)evals/history.json,evals/report/assessment.md) left unchanged as they document past runsSyntax fixes
data-types.mdGENERATOR_INDEX__NOTE_HASH→DOM_SEP__NOTE_HASHnotes.mdowner/randomnessfrom#[note]struct (macro handles these)notes.mdUintNote::new(amount, owner)→UintNote { value: amount }(no constructor exists)notes.mdU128→u128notes.mdself.emit(note, recipient, ...)→.insert(note).deliver_to(recipient, ...)notes.mdDeserialize, Eq, Packable, Serialize) matching upstreampartial-notes.md.call(&mut context)→self.call(), fixprepare_private_balance_increasearity (1 param, not 2)transaction-lifecycle.md.call(self.context)→self.call()Note on MCP server
The initial MCP sync reported success but served stale data from a different version, causing incorrect initial findings (e.g.
simulate_utilityinstead ofexecute_utility). All fixes were cross-checked againstgh apiwith?ref=v4.2.0-aztecnr-rc.2before finalizing. A forced re-sync resolved the MCP issue.Test plan
aztec_sync_repos({ version: "v4.2.0-aztecnr-rc.2", force: true })succeedsNargo.tomlandpackage.jsondeps resolve for the new version🤖 Generated with Claude Code