Skip to content

docs(upgrade): add example 0.1.5 upgrade guide - #4520

Draft
matthewgrossman wants to merge 1 commit into
mainfrom
docs/4398-upgrade-guide-example/matthewgrossman
Draft

matthewgrossman wants to merge 1 commit into
mainfrom
docs/4398-upgrade-guide-example/matthewgrossman

Conversation

@matthewgrossman

Copy link
Copy Markdown
Member

Summary

Example upgrade page for discussion in #4398. It shows how one release's upgrade guide could look, using #4497 as the only entry.

Related Issue

Related: #4398

Changes

  • Add docs/upgrade/0-1-5.mdx with one operator entry and one end-user entry.
  • Add the page to the Upgrade Guides nav above 0.1.0.

Open questions

  • Should each release get its own page, or should the guides use one running page?
  • Should releases with nothing to do still get a page saying "no action needed"?
  • Who writes the entry: the PR author when the change merges, or the release owner when the release is cut?

Testing

  • mise run docs:nav
  • mise run docs:build:strict

Add an example per-release upgrade page with one operator and one end-user
entry, to give the upgrade-guide process discussion a concrete starting
point.

Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>
@copy-pr-bot

copy-pr-bot Bot commented Oct 13, 2026

Copy link
Copy Markdown

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@github-actions

Copy link
Copy Markdown

This branch has not been deployed

No deployments
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.

1 participant