v2.13.7 - Rancher Manager Release Maintenance Task Checklist

[btat]

This issue is to track tasks that need to be done every release regardless of whether the release has new feature content or not.

Note

Links to published pages and source files are for reference only.

Apply updates be to the version and language appropriate files as needed.

• Create a new branch for the release, such as v2.12.1. Release-specific updates should use this branch as its base.
• Update the current-patch-version attribute in the antora.yml file.
• Update the release notes page tables:
  • Published page
  • Source
• Update the Rancher:webhook version mapping table:
  • Published page
  • Source
• Update the CNI popularity table partial:
  • Published page
  • Source
• Update the CSP adapter compatibility matrix:
  • Published page
  • Source
• Update the deprecated features table:
  • Published page
  • Source
• Update the swagger-<VERSION>.json file in versions/<VERSION>/modules/en/attachments/.
• Verify that documentation successfully builds in the release branch and then create a PR merging the release branch back into the main branch.
• If needed, submit a publish request for the staged content built in the gh-pages branch of the product-docs-playbook repo.
• Verify that documentation is successfully published on documentation.suse.com

Minor releases

The following apply to new minor releases only. E.g. v2.13 is introduced for the first time.

• Under versions/, create a new subfolder for the new minor version.
  • Copy the latest existing version.
  • In the new subfolder's antora.yml or antora-yml/* file(s), update the version field.
  • In the repository's playbook file(s):
    • Add the new version to the content.sources.start_paths field.
    • Update the component version of the site.start_page field.
• In the product-docs-playbook repository's playbook file(s), add the new version to the content.sources.start_paths field.