chore(deps): update engine to the account-store and prepare fix stack - #1607
chore(deps): update engine to the account-store and prepare fix stack#1607Dodecahedr0x wants to merge 1 commit into
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughChangesWorkspace dependency update
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The PR updates pinned engine dependencies and the lockfile while preserving the documented workspace behavior; no actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What changed
Pins every
magicblock-enginegit dependency and[patch.crates-io]entry to revec741da47eca2f43f5797dde2530640ecb12aa39, the tip of the engine fix stack (magicblock-labs/magicblock-engine#103, magicblock-labs/magicblock-engine#104, magicblock-labs/magicblock-engine#105), instead of tag0.3.1. Addsmagic-root-interfaceto the workspace dependency table (used later in this stack) and regeneratesCargo.lock. The dependency-table reformatting is from the workspace TOML formatter.Closes #1598
Impact
The validator picks up in-place account slot reuse, the
Prepareinstruction for missing writable action accounts, and the checksum-boundary index fsync. No validator code changes. The rev pin is a stopgap until the engine stack lands in a release tag.Reviewer notes
The rev must stay reachable on the engine remote (it is the head of the
dode/sync-on-checksumPR branch).cargo check --workspacepasses at this commit against the pinned rev.