Skip to content

feat(components): added new ReleaseNoteHeader component#4644

Open
flippedcoder wants to merge 2 commits into
mainfrom
mm/release-component
Open

feat(components): added new ReleaseNoteHeader component#4644
flippedcoder wants to merge 2 commits into
mainfrom
mm/release-component

Conversation

@flippedcoder
Copy link
Copy Markdown
Contributor

@flippedcoder flippedcoder commented Jun 2, 2026

What does this PR do?

This closes #4276 and implements a new component for release stage announcements on feature pages. The new component allows us to show which stage the feature is in, which languages are supported, and a few other customizations.

Notes to reviewers

Example of new ReleaseNoteHeader:

Screenshot 2026-06-02 at 12 13 10

┆Attachments: EDU-6459 feat(components): added new ReleaseNoteHeader component

@flippedcoder flippedcoder requested a review from a team as a code owner June 2, 2026 17:13
@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
temporal-documentation Ready Ready Preview, Comment Jun 2, 2026 5:13pm

Request Review

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 2, 2026

📖 Docs PR preview links

@bechols
Copy link
Copy Markdown
Contributor

bechols commented Jun 2, 2026

General suggestion I missed in my original PR: guidance/nudge for pre-release when users need to actively request to participate (i.e. the pre-release feature is invite-only). Doesn't apply for all pre-releases, but when it's the case, really important to avoid confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants