📝 docs(release): prepare v1.6.0-rc.7 - #609
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 24 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ 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 (16)
✨ 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 |
Routine pre-cut sync: takes `dev/v1.6` (`391c1b7d`) wholesale onto `main` so the rc.7 tag cuts from a tree identical to the dev branch. Delta since the rc.6 sync (#603): - #607 — four identity-drift fixes (soak-clock recreate reset, notification dedup double-fire, scan write-back revert, update-age fallback leak) - #608 — icon-bundle regenerated against the locked iconify versions - #609 — rc.7 release-surface prep (CHANGELOG heading, 17-file identity bump) Head branch is a throwaway (`sync/main-20260726-rc7`), not `dev/v1.6`, so auto-delete-head-branches can't touch the dev branch (#596 lesson). <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Changelog - 🐛 Fixed identity drift across maturity tracking, notification deduplication, and scan write-back. - 🐛 Prevented stale or removed containers from being overwritten or resurrected during scans. - ✨ Added shared candidate-identity extraction and raw-container access APIs. - 🔧 Updated maturity/age filtering and sorting behavior and expanded regression coverage. - 🔧 Regenerated the server icon bundle. - 🔧 Bumped release surfaces, documentation, mocks, and validation tests from `v1.6.0-rc.6` to `v1.6.0-rc.7`. - ✨ Added `v1.6.0-rc.7` release highlights and GA-compatible release-surface checks. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
1 participant
Prepares the release surfaces for cutting
v1.6.0-rc.7. No runtime code changes.Why now
rc.6 published clean earlier today, but the same day's identity-drift sweep produced four runtime fixes (#607) plus the icon-bundle regen (#608). A runtime change forces a new candidate and restarts the seven-day soak, so rc.7 it is.
What's here
Changelog. Promotes
[Unreleased]to[1.6.0-rc.7] — 2026-07-26sorelease-cut.yml's CHANGELOG validation resolves an entry for the tag. The four Fixed entries came in with #607; this adds the Changed entry for #608 and the link definitions.Release identity. The usual 17-file bump: version badge,
site-config.ts, the roadmap entry insite-content.ts, demo mock fixtures, the API doc response samples, the quickstart tag matrix, a new highlights section on the updates page, and the three pinned identity tests underscripts/. The README highlights block keeps the cumulative v1.6 feature list, matching the rc.6 prep pattern (badge + summary line bump only).All eight version files already sit at the
1.6.0base, so nopackage.jsonbump is needed.Verification
node --teston the four identity/changelog scripts: 24 pass, 0 fail