Update v6.6 changelog in prep to cut rc4#3765
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
bdchatham
added
non-app-hash-breaking
backport release/v6.6
PR SummaryLow Risk Overview Documents #3757 (backport: route EVM validation failures to giga v2 fallback, CON-368) and #3748 (version bump ahead of v6.6-rc3). Docs-only — no runtime or config changes in this PR. Reviewed by Cursor Bugbot for commit 4700cfb. 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).
|
![seidroid[bot]](https://avatars.githubusercontent.com/in/2745135?s=60&v=4){kind=small}
There was a problem hiding this comment.
Docs-only PR adding two v6.6 changelog entries. Both entries (#3757 and #3748) exactly match the referenced PRs' titles and are placed in correct descending PR-number order at the top of the v6.6 section. No code changes and nothing of concern.
Findings: 0 blocking | 2 non-blocking | 0 posted inline
Blockers
- None at the file/PR level.
Non-blocking
- The Cursor second-opinion review file (cursor-review.md) is empty — that pass produced no output. The Codex review reported no material issues.
- Verified the two added changelog lines match the actual GitHub titles of PR #3757 ("Backport release/v6.6: fix(giga): route EVM validation failures to v2 fallback (CON-368)") and PR #3748 ("Bump version in prep to release v6.6-rc3"), and that ordering is correct.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
LGTM — docs-only changelog update, entries match the referenced PRs (#3757, #3748) and the version-ordering convention used by prior rc changelog entries.
What was reviewed: Confirmed the two new lines reference real, already-merged PRs (#3757 backport of CON-368, #3748 rc3 version bump) and are inserted in the correct chronological position at the top of the v6.6 section. No code, config, or logic changes in this PR.
Extended reasoning...
Overview
Single-file change to CHANGELOG.md adding two entries to the v6.6 section, documenting PR #3757 (backport of the CON-368 EVM validation fallback fix) and #3748 (rc3 version bump). This is prep work for cutting v6.6.0-rc4 and lands on main first before being backported to release/v6.6 via the label.
Security risks
None. This is a documentation-only change with no code, configuration, or build logic affected.
Level of scrutiny
Minimal scrutiny is appropriate here — it's a two-line addition to a markdown changelog file, following an established pattern from prior rc changelog PRs (rc2, rc3) visible in the same file. There is no ambiguity or design decision involved.
Other factors
No prior review from me exists on this PR. The referenced PR numbers correspond to real, already-merged changes (confirmed via recent commit history: CON-368 fix commit 65411b1 is in the log). No outstanding review comments to address.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3765 +/- ##
==========================================
- Coverage 59.88% 58.95% -0.93%
==========================================
Files 2288 2201 -87
Lines 190023 180180 -9843
==========================================
- Hits 113786 106234 -7552
+ Misses 66091 64601 -1490
+ Partials 10146 9345 -801
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
1 participant
Adds the v6.6 changelog entries for the changes landed on
release/v6.6since the rc3 changelog update (#3744):release/v6.6: fix(giga): route EVM validation failures to v2 fallback (CON-368) #3757 — Backport of the CON-368 fix (route EVM validation failures to v2 fallback)Lands on
mainfirst per the release runbook; thebackport release/v6.6label auto-opens the backport into the release branch.Prep for cutting v6.6.0-rc4. Docs-only; no code change.
🤖 Generated with Claude Code