Repository navigation
chore: bump version to 0.47.0 - #1405
Conversation
|
✅ Review complete in 1m 5s Planner (6s) Review (supply_chain · pair): 0 findings Judge: 0 kept · 0 dropped (22s) Review metadataConfig:
Account limits:
Timing:
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
Waiting for bot review — coderabbitai not yet. Wait for the missing reviews, or a writer can post |
There was a problem hiding this comment.
✅ Approved.
What this does: Writes the release notes for version 0.46.0 into the changelog, with highlights and the PR and author behind each entry. It also moves the workspace version number to 0.47.0 for the next development cycle.
What to test
The review model wrote these steps. Check what a step runs before you follow it.
- Run
cargo metadata --no-deps --format-version 1at the root. Expect every workspace crate to report version0.47.0. - Open
CHANGELOG.md. Expect an empty## Unreleasedheading followed by## 0.46.0 - 2026-11-13. - Read the
0.46.0section. Expect one### Added, one### Changed, one### Fixedand one### Removedheading, with no duplicates. - Search the
0.46.0section forkey-wallet-ffi,dash-spv-ffiandtaproot. Expect them only in theRemovedentries. - Check the git tag this lands under. Expect the
0.47.0version bump not to be on the commit taggedv0.46.0.
About this review
- Reviewed
2309a6a, round 1 - 320 changed lines read in 1m 5s
- Found by
claude-sonnet-5-5andclaude-opus-5-5, judged byclaude-opus-5-5 - Tokens: 515k in (252k from cache) · 4k out · about $1.20 at API prices
- How Manki reviews
|
Bots are done — your move: post |
5b2a788
|
✅ Review complete in 1m 49s Planner (7s) Review (supply_chain · pair): 0 findings Judge: 1 kept · 0 dropped (38s) Review metadataConfig:
Account limits:
Timing:
Last reviewed
|
|
Waiting for bot review — coderabbitai not yet. Wait for the missing reviews, or a writer can post |
There was a problem hiding this comment.
🔴 Changes requested: 1 new blocker.
What blocks: This PR dates the 0.46.0 changelog section as the release and also raises the workspace version from 0.46.0 to 0.47.0. When it merges into master and is tagged v0.46.0, every crate at that tag reports 0.47.0.
About this review
- Reviewed
5b2a788, round 2 - 320 changed lines read in 1m 49s
- Found by
claude-sonnet-5-5andclaude-opus-5-5, judged byclaude-opus-5-5 - Tokens: 904k in (641k from cache) · 8k out · about $1.37 at API prices
- How Manki reviews
There was a problem hiding this comment.
✅ Approved. All blocking threads are resolved.
Findings dismissed by a repo admin: The 0.46.0 release commit declares the workspace version as 0.47.0 by @xdustinface.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #1405 +/- ##
==========================================
- Coverage 85.81% 85.79% -0.03%
==========================================
Files 269 269
Lines 70847 70851 +4
==========================================
- Hits 60799 60787 -12
- Misses 10048 10064 +16
|
|
Bots are done — your move: post |
…run 43527079468)
Opens the
0.47.0development cycle ondevnow thatv0.46.0is released frommaster.0.47.0.0.46.0changelog section, identical to the one onmaster, in place of the oldUnreleasedsection.Nothing else from the release branch needs to come back to
dev: the release isdevatc9aeac0d0plus the changelog. PRs merged afterc9aeac0d0go into the0.47.0changelog.PR Hygiene ·
5b2a788/self-reviewedWhen every merge requirement is met, the
PR Hygienecheck passes. Reviewer limits do not block merging; other required GitHub checks and protections still apply.