release: consolidate 0.6.0 changelog for v0.6.0 tagging - #389
release: consolidate 0.6.0 changelog for v0.6.0 tagging#389seonghobae wants to merge 20 commits into
Conversation
Fold Unreleased entries into the [0.6.0] section (2026-08-25): theme-token catalog, accessibility accent/focus fixes, security floors, and the gap baseline doc; reword active-PR evidence phrasing to protected-integration truth. Docs-only change on top of #384's snapshot-free baseline contract.
|
Warning Review limit reachedNext included review available in 56 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough0.6.0 릴리스 항목을 Changes릴리스 및 문서 갱신
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This PR updates release documentation and its consistency checks without changing product or runtime behavior; no actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
ADR 0031 Accepted (integrated via #362); UML/adr-index/storybook-inventory/ doctoring/design-tokens moved from Active-PR phrasing to shipped truth; designTokenDocumentation.test.ts asserts the integrated contract.
|
All exact-head gates terminal success (24 checks). Merging via the organization admin path; |
|
Fresh release-gate evidence for current head 82f4de6 against protected main 128a239:
|
|
Please review the exact current head |
|
Central exact-source/dependency-review control-plane repair is now protected on Do not transfer predecessor aggregate-green evidence. Require actual exact-head Dependency Review execution, exact submitted-head Trivy/SAST/source identity, successful sidecar health followed by real Noema/Strix/OpenCode execution, and a formal current-head verdict. Keep automated verdicts separate from the live non-author counted approval requirement. @cwl-noema-review review |
|
@opencode-agent review Central exact-source / Dependency Review control-plane repair is now protected at Do not carry predecessor verdicts or aggregate-green evidence forward. Keep automated semantic verdict, exact-source/security evidence, and the separately required non-author counted human approval distinct. This request is not merge or release authorization. |
Purpose
Prepares the
v0.6.0release metadata by folding the former Unreleased entries (theme-token catalog + Storybook inventory, accessibility accent/focus fixes, transitive security floors, and the product-gap baseline) into the dated[0.6.0] — 2026-08-25section and reconciling design-token documentation with behavior already integrated on protectedmain.Scope
Release documentation plus executable release/documentation contracts:
CHANGELOG.md, the design-token/Storybook ADR and operator documentation,src/designTokenDocumentation.test.ts,src/unifiedReleaseVersion.test.ts, andscripts/release-metadata.test.mjs. No editor/runtime/package behavior, dependency, transport, persistence, credential, model, tenancy, or deployment authority changes here; package versions remain0.6.0.The documentation contracts require the operator guide, ADR index, Storybook inventory, doctoring record, UML, changelog category boundaries, Unreleased sentinel, and current package release heading to agree with protected-main shipped truth. A branch ref is not release identity. Merge does not by itself authorize tagging or publication: issue #118 remains the canonical operational acceptance boundary, and the exact protected head must satisfy then-live review, required-workflow, security, package/SBOM/provenance, release, and registry-digest requirements before a
v0.6.0tag or publication.Summary by CodeRabbit