📝 docs(release): prepare v1.6.0-rc.6#602
Merged
Merged
Conversation
Promotes the [Unreleased] heading to [1.6.0-rc.6] so release-cut's CHANGELOG validation resolves an entry for the tag, and records the rest of the delta since rc.5: the dependency maintenance wave, the Crowdin translation resync, and the three CI/repo fixes (#599, #594, #593) that landed without changelog entries of their own. All eight version files already sit at the 1.6.0 base, so no bump is needed for this RC.
Advances the badge, site config, roadmap entry, demo fixtures, API doc samples, quickstart tag matrix, and the pinned release-identity tests from rc.5 to rc.6, and adds the rc.6 highlights section to the updates page.
scttbnsn
requested review from
ALARGECOMPANY and
biggest-littlest
as code owners
July 26, 2026 18:33
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
📝 WalkthroughWalkthroughUpdated release references from Possibly related PRs
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
scripts/release-docs-identity.test.mjs (1)
26-35: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winKeep release identity expectations on one source of truth.
Both test files duplicate candidate literals while already maintaining an
RC_VERSIONconstant. Derive positive fixtures and boundary negatives from that constant, while keeping the constant itself as the single pinned candidate value.
scripts/release-docs-identity.test.mjs#L26-L35: derive badge, highlight, API, and quickstart expectations fromRC_VERSION.scripts/release-identity.test.mjs#L66-L78: derive positive, boundary-negative, and extraction fixtures fromRC_VERSION.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@scripts/release-docs-identity.test.mjs` around lines 26 - 35, Use RC_VERSION as the sole pinned candidate value in scripts/release-docs-identity.test.mjs lines 26-35: derive badge, highlight, API, and quickstart positive and boundary-negative assertions from it instead of duplicating version literals. Apply the same change to scripts/release-identity.test.mjs lines 66-78, deriving its positive, boundary-negative, and extraction fixtures from RC_VERSION while leaving that constant as the single source of truth.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@scripts/release-docs-identity.test.mjs`:
- Around line 26-35: Use RC_VERSION as the sole pinned candidate value in
scripts/release-docs-identity.test.mjs lines 26-35: derive badge, highlight,
API, and quickstart positive and boundary-negative assertions from it instead of
duplicating version literals. Apply the same change to
scripts/release-identity.test.mjs lines 66-78, deriving its positive,
boundary-negative, and extraction fixtures from RC_VERSION while leaving that
constant as the single source of truth.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: dd0a13a8-d0b7-4821-bae4-5d0f8924c61b
⛔ Files ignored due to path filters (1)
CHANGELOG.mdis excluded by!CHANGELOG.md
📒 Files selected for processing (16)
README.mdapps/demo/src/mocks/data/agents.tsapps/demo/src/mocks/data/audit.tsapps/demo/src/mocks/data/containers.tsapps/demo/src/mocks/data/server.tsapps/demo/src/mocks/handlers/app.tsapps/web/src/lib/site-config.tsapps/web/src/lib/site-content.tscontent/docs/current/api/agent.mdxcontent/docs/current/api/app.mdxcontent/docs/current/api/portwing.mdxcontent/docs/current/quickstart/index.mdxcontent/docs/current/updates/index.mdxscripts/changelog-links.test.mjsscripts/release-docs-identity.test.mjsscripts/release-identity.test.mjs
CodeRabbit flagged that both identity tests duplicated the candidate version literal roughly 26 times alongside an RC_VERSION constant that already existed, which is why every RC bump has been an error-prone hand-edit across the whole file. RC_VERSION, plus a new PREV_RC_VERSION for the changelog compare link, are now the single source of truth. Positive assertions, boundary negatives, and inline fixtures all derive from them, including the shields.io double-dash badge form and the quickstart negative lookahead. The 1.5.0 matcher-generalization case and the 1.5.2 archive references stay literal: they pin the archived line, not the release identity. Verified both directions. Pointing RC_VERSION at an unreleased rc.7 fails against the real on-disk files, and reverting the README badge to rc.5 with RC_VERSION correct also fails, so the assertions still read real files rather than comparing derived strings to themselves.
Contributor
Author
|
Good catch, took it. Both files now derive everything from Left Verified it didn't go tautological, in both directions: pointing
|
scttbnsn
added a commit
that referenced
this pull request
Jul 26, 2026
Routine dev → main sync ahead of cutting `v1.6.0-rc.6`. Per the branch model, `main` only advances by merging from `dev/v1.6`, never by taking independent commits, and the cut is dispatched from `main`. Opened from a throwaway `sync/main-rc6` branch rather than from `dev/v1.6` directly. Auto-delete-head-branches deleted `dev/v1.6` when sync PR #596 used it as the head, which is what broke the Crowdin sync. ## Content The entire delta is the rc.6 prep merged in #602: the dated `[1.6.0-rc.6]` changelog entry and the 16-file release identity bump. ## Conflict resolution The three-way merge conflicted on `CHANGELOG.md`. That's an artifact of squash-merge-only ancestry — `main` picked up the same content through an earlier squash, so the merge reads both sides as independently adding it. Resolved with `git merge -s ours origin/main`, which takes `dev/v1.6`'s tree wholesale. Verified that loses nothing: - No file exists only on `main` - The complete content diff between `main` and `dev/v1.6` is exactly the 17 rc.6 prep files, nothing else After the merge, `git diff HEAD origin/dev/v1.6` is empty, so this branch's tree is byte-identical to `dev/v1.6`. That's the invariant the release-cut drift guard asserts. ## Verification - Full pre-push gate green: qlty, qlty-smells, scripts-test, workflow-tests, typecheck-ui, web-scripts-test, coverage, build, zizmor - `renovate.json` already targets `dev/v1.6`, so the drift guard's bot-target assertion passes - All eight version files sit at the `1.6.0` base that the tag validation expects Next after merge: dispatch `release-cut.yml --ref main -f release_tag=v1.6.0-rc.6`. --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the release surfaces for cutting
v1.6.0-rc.6. No runtime code changes.Why now
rc.5 was cut on 2026-07-23. Since then
dev/v1.6picked up #587, the maturity-cleared notification — a new feature, not a fix, with a newmaturity-policymodel, ~170 lines inTrigger.ts, ~100 instore/container.ts, and a new background sweep on a newDD_MATURITY_SWEEP_CRONdefault. On top of that the delta carries a full dependency bump wave across all six lockfiles plus a Crowdin translation resync.That's too much unsoaked change to take straight to GA, so it gets an RC first.
What's here
Changelog. Promotes
[Unreleased]to[1.6.0-rc.6] — 2026-07-26sorelease-cut.yml's CHANGELOG validation resolves an entry for the tag, and backfills the rest of the delta since rc.5: the dependency wave, the translation resync, and the three CI/repo fixes (#599, #594, #593) that landed without changelog entries of their own.Release identity. The usual 16-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/.All eight version files that
release-cut.ymlchecks already sit at the1.6.0base, so nopackage.jsonbump is needed for this RC.Verification
node --test scripts/*.test.mjs— 133 pass, 0 failmainanddev/v1.6trees were in sync before this branch, so the pre-cut drift guard only needs the one sync after mergeChangelog
✨ Added
v1.6.0-rc.6highlights (maturity-cleared notifications, dependency + translation resync, CI scripting robustness) for July 26, 2026.🔧 Changed
v1.6.0-rc.6release surface by updating version identity references fromv1.6.0-rc.5→v1.6.0-rc.6across README, site config/content, roadmap/demo content, API documentation samples, quickstart tags, and the updates page.1.6.0-rc.6consistently (agent, audit, container, server, and API handler fixtures).RC_VERSION, addedPREV_RC_VERSIONfor changelog compare-chain links, and ensured archived release references remain literal.v1.6.0-rc.6as the chain head and added thev1.6.0-rc.6expected compare range (v1.6.0-rc.5...v1.6.0-rc.6).RC_VERSIONmatches-rc.<number>before deriving prefix/number.Concerns
v1.6.0-rc.6, 2026-07-26) is correctly updated everywhere it’s generated/linked (docs + compare-link tests).1.5.0/1.5.2references remain literal in identity tests (to avoid unintended tautologies).rc.6token with no remainingrc.5stragglers.