Skip to content

Add release announcement field to the Communications handbook#2987

Open
kfess wants to merge 1 commit intokubernetes:masterfrom
kfess:feature/add-frontmetter
Open

Add release announcement field to the Communications handbook#2987
kfess wants to merge 1 commit intokubernetes:masterfrom
kfess:feature/add-frontmetter

Conversation

@kfess
Copy link
Copy Markdown
Member

@kfess kfess commented Apr 3, 2026

What type of PR is this:

/kind documentation

What this PR does / why we need it:

Add documentation for the release_announcement field in the release blog frontmatter to the Communications handbook.

This field is being introduced in kubernetes/website#54885 to support the automated release series page generation. The release series pages (e.g., /releases/1.35/) will automatically link to the corresponding release announcement blog post using this frontmatter field.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

The release series pages (e.g., https://kubernetes.io/releases/1.35/) are now auto-generated from existing data (kubernetes/website#54041). To automatically display a link to the release blog on these pages, PR (kubernetes/website#54885) is trying to add support for the release_announcement field in the blog frontmatter.

As suggested in kubernetes/website#54885, this PR updates the handbook so future Comms leads know to add this field.

@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. needs-priority labels Apr 3, 2026
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kfess
Once this PR has been reviewed and has the lgtm label, please assign chadmcrowell for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added area/release-team Issues or PRs related to the release-team subproject sig/release Categorizes an issue or PR as relevant to SIG Release. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Apr 3, 2026
@rytswd
Copy link
Copy Markdown
Member

rytswd commented Apr 4, 2026

/hold

We are in the middle of the cycle for v1.36, and would want to keep the handbook changes to minimum.
We will keep in mind about this new frontmatter handling in the upcoming release announcement though 👍

FYI @chadmcrowell

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 4, 2026
@kfess
Copy link
Copy Markdown
Member Author

kfess commented Apr 5, 2026

Sure! Would be great if you could revisit this once the v1.36 release is done. Thanks!

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

Labels

area/release-team Issues or PRs related to the release-team subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/documentation Categorizes issue or PR as related to documentation. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants