1.8 KiB
| title | linkTitle | weight | type |
|---|---|---|---|
| Releasing a version of the Knative documentation | Release process | 75 | docs |
This document describes how to perform a docs release. In general, this should be done by one of the release managers in the list at https://github.com/knative/release.
Check Eventing, Serving, Client, and Operator
Have they all built releases (since the website references these release pages in various locations)?
Create a release branch
Using the GitHub UI, create a release-X.Y branch based on main. Check on
the #docs channel to make sure the release is ready. In the future, we
should automate this so the check isn't needed.
Update the main branch to reference the release
hack/build.sh
Find the references to the previous release number and update the lines to include the new release number as well. We keep the last 4 releases available per our support window, so clean up old versions at the end of the list when there will be more than 4.
Until the old hugo configuration has been aged out (after release 0.27), it's
best to send these PRs to @julz to double-check. You'll also want to remove the
appropriate directory of hugo content under archived/vX.Y-docs for the oldest
version, i.e. 0.26 release removed the archived/v0.22-docs.