chore(release): v0.3.0-alpha#644
Conversation
Move the accumulated Unreleased notes into a dated 0.3.0-alpha section ahead of the release branch version bump. * Record the native shielded token standard (MIP-0011) with its opt-in supply and derived-nonce extensions (#621). * Add the audit fix for the zero-value revert findings L-01 and L-02 in the token modules (#616). * Add the async, backend-aware simulator migration that lets the unit suites run on both dry-run and live backends (#620, #631). * Correct the @openzeppelin/compact-simulator bump target to ^0.2.0 to match the shipped dependency.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (41)
WalkthroughBumps the package version from Changesv0.3.0-alpha Release Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related issues
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Types of changes
What types of changes does your code introduce to OpenZeppelin Midnight Contracts?
Put an
xin the boxes that applyFixes #???
Release PR for
v0.3.0-alpha, targetingmainperRELEASING.md.Pushing the
release-v0.3.0-alphabranch triggers theprepare-release.ymlworkflow, which bumps the version incontracts/package.jsonand the// OpenZeppelin Compact Contracts vX.Y.Zheaders throughoutcontracts/src/(0.2.0→0.3.0-alpha) and commits it to this branch. This PR is the review gate for those changes before the tag is cut.This pre-release bundles everything merged since
v0.2.0. Changelog summary:Added
MIP-0011, with opt-in supply and derived-nonce extensions (feat(token): add native shielded token standardMIP-0011#621)Changed
0.29.0→0.31.0,pragma language_version>= 0.21.0→>= 0.23.0, runtime / ledger / simulator bumps)Fixed
PR Checklist
Further comments
The CHANGELOG was updated manually (move
Unreleased→ dated0.3.0-alpha) ahead of the automated version bump, mirroring thev0.2.0release. Once this merges, follow the remainingRELEASING.mdsteps: pullmain, tagv0.3.0-alpha, push the tag, then publish the GitHub release.Summary by CodeRabbit
0.3.0-alphaand refreshed package metadata to match.