📝 docs(release): bump release identity to v1.6.0-rc.2#549
Merged
Conversation
- 📝 dated [1.6.0-rc.2] — 2026-07-18 CHANGELOG heading, fresh empty [Unreleased] section, and matching link-reference definitions - 📝 rc.2 version identity across README badge/highlights, website site-config/site-content timeline, updates page (new rc.2 highlights section), API doc example payloads, quickstart tag matrix, and the five demo runtime fixtures - ✅ guard tests updated in lockstep: release-identity, release-docs-identity (incl. the compare-base template moving to v1.6.0-rc.1...v1.6.0-rc.2), changelog-links
scttbnsn
requested review from
ALARGECOMPANY and
biggest-littlest
as code owners
July 17, 2026 03:06
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughUpdates release surfaces, demo fixtures, API examples, and release validation from Possibly related PRs
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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.
Inline comments:
In `@content/docs/current/updates/index.mdx`:
- Around line 6-10: Update the v1.6.0-rc.2 release heading in the updates
document so it does not use the future date July 18, 2026; use the actual
publication date of July 17, 2026, or defer the entire release entry until
publication on July 18.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: b2f398c4-c463-406c-8c6e-0b7a6fd85b26
⛔ 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
scttbnsn
added a commit
that referenced
this pull request
Jul 18, 2026
## Summary - consolidates the accepted v1.6.0-rc.2 delta from `dev/v1.6` over the shipped rc.1: the #541/#542/#543 error-rebuild hardening round 2 (PR #547), the #538 "Version Update" container filter (PR #539), the #544 workflow-test scaffolding dedupe (PR #548), and the rc.2 release identity sweep (PR #549) - restarts the soak: this is a new RC with a fresh 7-day clock and a fresh 24-hour NAS acceptance run, because #541–#543 change the exact watcher/store paths the run validates - excludes all private `.planning` changes from the release diff and history ## Immutable release construction - frozen base: `main` at `d6e166ff29d97d00215d7c69bfce91e3b5de3e8a` - frozen accepted tree: `dev/v1.6` at `51fea2cf22136a15ccef0be4a67b5dec8b009528` - release head: `d63b3d3e29ea21402ea4bf5474e997dbdc9af912` - release head parent is the frozen main SHA - commit count over frozen main is exactly one - non-planning tree matches the frozen `dev/v1.6` tree exactly (empty diff) - `.planning` is absent from frozen main and the release head and contributes zero files or commits - the 37-file main→dev delta attributes exactly to PRs #539/#547/#548/#549 — nothing unaccounted in either direction ## Local verification on the exact release head - complete pre-push gate passed in 272.44s - 105 maintenance tests - 31 workflow tests - 37 website-script tests (run manually — the push glob skips them) - backend and UI coverage at 100 percent - app and UI production builds - UI typecheck, Biome, accepted Qlty baseline, and Zizmor with zero findings (run manually — the push glob skipped it) - acceptance-harness `monitor.test.mjs` 7/7 locally - CodeRabbit reviews resolved on every constituent PR (#539, #546, #547, #548, #549) ## Final merge gate Do not merge this PR or cut `v1.6.0-rc.2` until the exact-head GitHub CI, Playwright, Cucumber, load/security matrix, CodeRabbit/Qlty/CodeQL review, two required non-author approvals, and the isolated fresh 24-hour NAS acceptance report are clean with `passed: true`. The 24-hour NAS run starts last from the frozen approved tree. After rc.2, the 7-day soak restarts from its publication date (GA earliest ~2026-07-25); GA promotes the exact RC digest, and any further code change requires a new RC and a fresh soak. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ✨ Added - Added shared GitHub Actions workflow testing utilities (`.github/tests/workflow-test-utils.ts`) with `loadWorkflow()`/`getWorkflowStep()` and workflow YAML types; refactored workflow inspection tests to use them. - Added/expanded Docker `watchContainer` Vitest coverage (`app/watchers/providers/docker/container-processing.test.ts`) to assert failure/success preservation of `result` and `currentReleaseNotes`, including validated-container getter safety. - Added/expanded Docker image orchestration tests for fast-path/repair-branch digest stickiness and errored-container fast-path eligibility (`docker-image-details-orchestration.*.test.ts`). - Added UI + i18n support for the new **“Version Update”** container filter (`filterKind="version"`), including kind-filter matching semantics, filter-chip/select option rendering, and route-query synchronization tests. - Added Portwing WS unit test assertions that the `welcome` frame’s `config.drydockVersion` matches the canonical `getVersion()` value (`app/api/portwing-ws.test.ts`). - Added/updated release-candidate identity/docs/changelog validation to cover `v1.6.0-rc.2` (including compare-link chain completion expectations). 🔧 Changed - Refactored workflow inspection tests to deduplicate YAML parsing/type scaffolding by using shared `loadWorkflow`/`getWorkflowStep` helpers and shared workflow typings. - Hardened `watchContainer` by snapshotting/restoring only `containerWithResult.result` and `containerWithResult.currentReleaseNotes` across watch cycles, restoring them only when the current cycle still produced no fresh `result` (so later enrichment failures don’t overwrite earlier successful comparison state). - Updated Docker orchestration logic: - Included errored containers in the “already in store” refresh path. - Adjusted digest repair/stickiness behavior in `refreshStoredContainerImageFields`. - Simplified returned `containerToReturn.image.digest.value` assignment to always use the computed `repoDigest`. - Removed the explicit `structuredClone` carry-over of `updatePolicyOverrides` into returned containers before applying declarative policy. - Updated Portwing WS version reporting to lazily populate the cached drydock version from `getVersion()` on first use; extended `injectDrydockVersionForTesting` to accept `string | undefined`. - Implemented `filterKind="version"` as a grouped match: containers with `updateKind` of `major`/`minor`/`patch` match the version filter. - Bumped `v1.6.0-rc.1` → `v1.6.0-rc.2` across release identity surfaces (README/site badge + highlights, demo/mock data, API docs, quickstart/update content) and updated release-doc/changelog identity tests accordingly. 🐛 Fixed - Fixed an E2E restore-path defect where restoring getter-derived fields could throw and prevent container report persistence; restoration now targets only `result`/`currentReleaseNotes` so validated-container getters can safely derive `updateAvailable`/`updateKind`. - Fixed/validated Portwing welcome/version correctness by ensuring the `welcome` frame uses `getVersion()` and adding direct unit coverage. 🔒 Security - Preserved registry-reconciled digest context through watch/compare failure paths to keep security-scan grouping stable.⚠️ Breaking - None⚠️ Concerns - Ensure exact-head CI, testing, security checks, and all required approvals/reviews pass before merging/publishing. - Re-run both prior E2E jobs if needed to confirm the Playwright failure was not flaky (previously attributed to CI 429 rate limiting). - Complete the fresh 24-hour NAS acceptance run before merging/publishing `v1.6.0-rc.2`. - Confirm the post-publication 7-day soak restart behavior matches the release plan. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
This was referenced Jul 21, 2026
Merged
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.
Release plumbing for the v1.6.0-rc.2 cut — the full identity bump the guard tests enforce (they correctly rejected a heading-only change twice):
[1.6.0-rc.2] — 2026-07-18CHANGELOG heading, fresh empty[Unreleased]section, matching link-reference definitionsv1.6.0-rc.1...v1.6.0-rc.2), changelog-linksVerified: 105/105 script tests, 37/37 website-script tests, full pre-push gate green.
rc.2 delta over rc.1: #538 version-update filter, #541/#542/#543 error-rebuild hardening round 2, #544 workflow-test dedupe, docs-alignment content from #546.
Last dev-side change before the release head freeze.
Changelog
🔧 Changed release identity from
v1.6.0-rc.1tov1.6.0-rc.2across README, website metadata, timeline, updates, API examples, quickstart, and demo fixtures.✨ Added the
v1.6.0-rc.2updates-page highlights and refreshed changelog headings/link references.🔧 Updated release documentation comparison base to
v1.6.0-rc.1...v1.6.0-rc.2.🔧 Updated release identity, documentation identity, and changelog-link guard tests for rc.2.
Verify the documented release date and all public version surfaces remain consistent.
Confirm the reported script, website-script, and pre-push test results in CI.