feat: state framework maturity and publish release notes - #4
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds a clear pre-1.0 maturity statement and a small set of release notes to both the docs landing page and the marketing homepage, with a shared data source and a regression test to keep the content from disappearing.
Changes:
- Introduces shared
maturityStatementandreleaseNotesdata for reuse across docs + marketing. - Renders new “Maturity” and “Release notes” sections on the
/docslanding page and wires them into the docs table of contents. - Adds a docs catalog regression test to ensure the maturity/release-note content remains present.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| tests/docs-catalog.test.ts | Adds regression assertions for maturity statement and release note presence. |
| src/pages/marketing/home.tsx | Displays the maturity statement on the homepage and links to the docs release notes anchor. |
| src/pages/docs/release-notes.ts | Centralizes maturity statement + release notes data for reuse. |
| src/pages/docs/page.tsx | Renders “Maturity” and “Release notes” sections on the docs landing page. |
| src/pages/docs/catalog.ts | Updates the docs landing table of contents to include the new sections. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
Summary
The dependency-updates guide already documents the concrete
askr updateversusaskr upgradebehavior; this PR surfaces that distinction from the release notes so upgrade expectations are not implicit.TDD
Validation
npm run checkgit diff --checkSquash merge requested.