Update v6.6 changelog in prep to cut rc3#3744
Conversation
PR SummaryLow Risk Overview The notable entry documents #3743 — backported range checks on No application code changes; release-process documentation only. Reviewed by Cursor Bugbot for commit efa8901. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).
|
There was a problem hiding this comment.
Documentation-only PR adding three changelog entries under v6.6 in prep for the rc3 cut; the entries match the PR description and referenced PRs, with correct formatting consistent with surrounding lines.
Findings: 0 blocking | 2 non-blocking | 0 posted inline
Blockers
- None at the file/PR level.
Non-blocking
- REVIEW_GUIDELINES.md is empty/missing, so no repo-specific guidelines were applied.
- Both second-opinion passes produced effectively no findings (Codex: "No material issues found in the three changelog additions."; Cursor: empty output).
There was a problem hiding this comment.
LGTM — documentation-only changelog update prepping v6.6.0-rc3.
What was reviewed:
- Three new bullets prepended under
## v6.6/ sei-chain, listing #3743 (CON-369 backport), #3732 (rc2 version bump), #3731 (rc2 changelog backport). - Ordering (newest-first) and format match the existing entries and prior rc-cut pattern.
- Referenced PR numbers align with the description; no other files touched.
Extended reasoning...
Overview
Single-file edit to CHANGELOG.md: three new bullet entries prepended to the ## v6.6 / sei-chain list in preparation for cutting v6.6.0-rc3. Entries capture #3743 (the CON-369 Dec range-check backport that motivates rc3) plus the two rc2 process commits (#3732 version bump, #3731 changelog backport), mirroring how the rc2 changelog handled the rc1 process commits.
Security risks
None. This is a documentation change with no runtime, consensus, dependency, or configuration impact.
Level of scrutiny
Minimal. Changelog-only edits carry no execution risk; verification is limited to checking that the referenced PR numbers, ordering, and formatting are consistent with the rest of the file, which they are.
Other factors
No prior review from me on this PR. The backport release/v6.6 label is set as expected for a v6.6 changelog change authored on main. Cursor bugbot also flagged it low risk. Nothing here warrants human gating.
fccf4b2 to
efa8901
Compare
There was a problem hiding this comment.
Changelog-only diff adding three release/v6.6 entries (#3743, #3732, #3731) in prep to cut v6.6.0-rc3. Entries are correctly placed at the top of the v6.6 section with valid PR links and no source-code impact.
Findings: 0 blocking | 1 non-blocking | 0 posted inline
Blockers
- None at the file/PR level.
Non-blocking
- Codex second-opinion review reported no material issues on this changelog-only diff. The Cursor second-opinion file was empty (no output produced); no impact given the doc-only nature of the change.
There was a problem hiding this comment.
LGTM — changelog-only prep for v6.6.0-rc3. Three new bullets at the top of the v6.6 section referencing merged PRs #3743, #3732, #3731. No runtime code touched.
Extended reasoning...
Overview
This PR adds three bullet points to CHANGELOG.md under the ## v6.6 section in preparation for cutting v6.6.0-rc3. The entries reference the immunefi/app-hash-breaking fix (#3743) plus two process commits from the rc2 cut (#3732 version bump, #3731 rc2 changelog backport). No other files are modified.
Security risks
None. This is a documentation-only change to a release changelog. No code, config, permissions, or dependencies are affected.
Level of scrutiny
Very low. Changelog-only edits carry no runtime risk. The referenced PR numbers correspond to real merged PRs on this repository, and the format mirrors the surrounding lines exactly. The pattern of listing both the substantive fix and the rc2 process commits also matches how rc2's changelog captured the rc1 process commits, as noted in the description.
Other factors
Buf checks are passing. Cursor bugbot flagged it as low risk documentation-only. The bug hunting system found no issues. The PR is small, self-contained, and follows the established changelog format used throughout the file.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3744 +/- ##
==========================================
- Coverage 59.89% 58.98% -0.91%
==========================================
Files 2288 2201 -87
Lines 189782 179951 -9831
==========================================
- Hits 113668 106146 -7522
+ Misses 65971 64464 -1507
+ Partials 10143 9341 -802
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
Successfully created backport PR for |
Adds the
release/v6.6entries merged since the rc2 changelog (#3730), in prep to cut v6.6.0-rc3:feat(cosmos): range-check Dec conversions and DecCoin validation (CON-369)(the immunefi/app-hash-breaking fix that motivates rc3)The two process commits mirror how the rc2 changelog (#3730) captured the rc1 cut's process commits (#3688 version bump, #3686 changelog). Authored on
main; thebackport release/v6.6label will trigger the backport to the release branch, after which theversion.jsonrc3 bump can cut the tag.🤖 Generated with Claude Code