This issue can be closed when we have completed the following steps (in order).
Please ensure all artifacts (PRs, workflow runs, Tweets, etc) are linked from
this issue for posterity. Refer to this prior release issue for
examples of each step, assuming vX.Y.Z is being cut.
[x] Run the Tag workflow on the release-X.Ybranch with the proper release version, vX.Y.Z. Message suggested, but not required: Release vX.Y.Z.
[x] Run the CI workflow on the release branch and verified that the tagged build version exists on the releases.crossplane.iobuild channel, e.g. build/release-X.Y/vX.Y.Z/... should contain all the relevant binaries.
[x] Confirm the full set of patch versions that will be released and promote them from lowest to highest, so the highest version is the last to be promoted (e.g. v1.12.2 should be promoted after v1.11.3), in order to avoid the promote workflow overwriting the latest patch release.
NOTE: This ordering requirement can be avoided by checking the "pre-release" checkbox in the promote workflow for the older releases, as described in #5420.
[x] Run the Promote workflow with channel stable on the release-X.Y branch and verified that the tagged build version exists on the releases.crossplane.iostable channel at stable/vX.Y.Z/....
[x] Published a new release for the tagged version, with the same name as the version and descriptive release notes, taking care of generating the changes list selecting as "Previous tag" vX.Y.<Z-1>, so the previous patch release for the same minor. Before publishing the release notes, set them as Draft and ask the rest of the team to double check them.
This issue can be closed when we have completed the following steps (in order). Please ensure all artifacts (PRs, workflow runs, Tweets, etc) are linked from this issue for posterity. Refer to this prior release issue for examples of each step, assuming vX.Y.Z is being cut.
release-X.Ybranch with the proper release version,vX.Y.Z. Message suggested, but not required:Release vX.Y.Z.buildchannel, e.g.build/release-X.Y/vX.Y.Z/...should contain all the relevant binaries.v1.12.2should be promoted afterv1.11.3), in order to avoid the promote workflow overwriting the latest patch release.stableon therelease-X.Ybranch and verified that the tagged build version exists on the releases.crossplane.iostablechannel atstable/vX.Y.Z/....vX.Y.<Z-1>, so the previous patch release for the same minor. Before publishing the release notes, set them as Draft and ask the rest of the team to double check them.