Merge pull request #5073 from mloskot/patch-1

docs: Mention Flux upgrade guide in release notes
pull/5071/head
Stefan Prodan 2 months ago committed by GitHub
commit 9f854cb7e2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

@ -43,6 +43,9 @@ The following template can be used for the GitHub release page:
<!-- auto-generated list of pull requests to the CLI starts here --> <!-- auto-generated list of pull requests to the CLI starts here -->
``` ```
Typically, you want to link the [Flux upgrade](https://fluxcd.io/flux/installation/upgrade/)
guide to refer users for up to date information on upgrade options.
In some scenarios, you may want to include specific information about API In some scenarios, you may want to include specific information about API
changes and/or upgrade procedures. Consult [the formatting of changes and/or upgrade procedures. Consult [the formatting of
`v2.0.0-rc.1`](https://github.com/fluxcd/flux2/releases/tag/v2.0.0-rc.1) for `v2.0.0-rc.1`](https://github.com/fluxcd/flux2/releases/tag/v2.0.0-rc.1) for
@ -69,4 +72,4 @@ The following template can be used for the Slack release message:
``` ```
For more concrete examples, see the pinned messages in the [Flux Slack For more concrete examples, see the pinned messages in the [Flux Slack
channel](https://cloud-native.slack.com/archives/CLAJ40HV3). channel](https://cloud-native.slack.com/archives/CLAJ40HV3).

Loading…
Cancel
Save