Repository navigation
chore(release): update changelog and bump version to 5.1.0-dev.1 - #5912
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 10 minutes. View limit details
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. |
|
Waiting for bot review — thepastaclaw not yet. Wait for the missing reviews, or a writer can post |
The release script ran in a git worktree, where `.git` is a file, so conventional-changelog could not read the origin URL and rendered every link of the new section as `undefined/undefined/undefined/issues/N` (and the compare link as `///compare/...`), leaving `closes #N` references unlinked. Regenerated the section from v5.0.3 at the same commit (e603d8a) with the repository URL supplied explicitly. The entries and their order are unchanged; only the links differ. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Feature PRs on v5.1-dev wrote detailed notes under a hand-written `## [Unreleased]` heading. The release script prepends the generated section above it, which left those notes as a stale [Unreleased] block between 5.1.0-dev.1 and 5.0.3. All of them describe v5.1-dev-only changes that ship in this release, so the block becomes a `### Notes` subsection of 5.1.0-dev.1, with its Tests / Fixed / Changed headings one level down. No note text changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
🕓 Review not started yet because the new head is waiting for the 30-minute push debounce.
Commit a36c9e0. Normal review starts when eligible; priority review starts as soon as a slot is available. |
Issue being fixed or feature implemented
Release new Dash Platform version
What was done?
How Has This Been Tested?
None
Breaking Changes
None
Checklist:
For repository code-owners and collaborators only
Quorum-proof checkpoints
Each moved checkpoint is proven from the one it replaces. Reviewers: check each new block hash at its height on a block explorer.
none of 5 seed evonodes gave an authenticated Platform Core height, for example https://65.109.108.141:443: quorum source unavailable: could not prove quorum 0000000000000016d05699f6ddf7ede9e7ce3a0949df14d4df8d5a881e683dce of type 4 for core height 2571571 within 203 ms: https://quorums.mainnet.networks.dash.org: HTTP 403 after 203 ms; every source is cooling down or out of this fetch0000005f9eaa8b84ae9447a208f7907e6bbe6b016a61aa35a6d63a43ba927019), verified tip 1590887, Platform at 1590887 (5 of 5 seed evonodes gave a verified height)PR Hygiene ·
84dfd02/skip-botsproceeds without the ones not yet reported/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.