Cut v1.12.0-up.1 Release on May 9, 2023

[jeanduplessis]

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. Assuming vX.Y.0-up.1 is being cut, after upstream crossplane/crossplane vX.Y.0 has been released according to the declared schedule, you should have:

• [ ] Created, or synced if already present, the release-vX.Y release branch in upbound/crossplane, with upstream crossplane/crossplane release branch, up to the vX.Y.0 tag, adding any required change specific to the fork, see here for more details.
• [ ] Cut upbound/crossplane vX.Y.0-up.1 release from the release-X.Y branch by:
  • [ ] Running the Tag workflow on the release-vX.Y branch with the proper release version, vX.Y.0-up.1. Message suggested but not required: Release vX.Y.0-up.1.
  • [ ] Running the CI workflow on the release-vX.Y branch to build and publish the latest tagged artifacts.
  • [ ] You should now be able to run: docker pull upbound/crossplane:vX.Y.0-up.1
• [ ] Created and merged a PR to the main branch of upbound/universal-crossplane with the following changes, taking care to label it as backport release-X.Y:
  • [ ] Update any reference to the old latest release to vX.Y.0-up.1, such as CROSSPLANE_TAG and CROSSPLANE_COMMIT in the Makefile.
  • [ ] Run make helm.prepare to import any change to the templates in the upstream Helm chart.
  • [ ] Manually diff and sync upstream's and uxp's values.yaml.tmpl as needed, taking care to change any required templating reference, e.g. %%CROSSPLANE_TAG%% instead of %%VERSION%%. E.g. export RELEASE_BRANCH=release-X.Y; vimdiff https://raw.githubusercontent.com/upbound/crossplane/$RELEASE_BRANCH/cluster/charts/crossplane/values.yaml.tmpl cluster/charts/universal-crossplane/values.yaml.tmpl.
  • [ ] Run make olm.build to generate the [OLM] bundle.
• [ ] Created the release-X.Y branch from main branch in UXP.
• [ ] Cut UXP vX.Y.0-up.1 release from the release-X.Y branch by:
  • [ ] Running the Tag workflow on the release-vX.Y branch with the proper release version, vX.Y.0-up.1. Message suggested but not required: Release vX.Y.0-up.1.
  • [ ] Running the CI workflow on the release-vX.Y branch to build and publish the latest tagged artifacts.
• [ ] Cut the next prerelease of UXP from the main branch, vX.<Y+1>.0-up.1-rc.1 by:
  • [ ] Running the Tag workflow on the main branch with the proper release version, vX.<Y+1>.0-up.1-rc.1. Message suggested but not required: Release vX.<Y+1>.0-up.1-rc.1.
• [ ] Run the Promote workflow to promote vX.Y.0-up.1 to stable, it should contain universal-crossplane-X.Y.0-up.1.tgz. Verify everything is correctly working by running up uxp install against an empty Kubernetes cluster, e.g. kind create cluster, which should result in an healthy UXP installation with expected image versions.
• [ ] Created and published well authored release notes for UXP vX.Y.0-up.1. See the previous release for an example, these should at least:
  • [ ] enumerate relevant updates that were merged in u/xp and u/uxp.
  • [ ] mention the xp/xp version it refers to.
  • [ ] list new contributors to u/uxp.
  • [ ] have the links to the full changelog of u/xp and u/uxp.
• [ ] Ensured that users have been notified of the release on all communitcation channels:
  • [ ] Slack: crossposting on Crossplane's Slack workspace channels #announcements, #upbound and #squad-crossplane on Upbound's Slack.
  • [ ] Twitter: ask #marketing on Upbound's Slack to do so.

[turkenh]

Closing this in favor of https://github.com/upbound/universal-crossplane/issues/369 because:

• It has some recent updates in the release process template
• It follows the patch release template since we already cut the release branch etc. in https://github.com/upbound/universal-crossplane/issues/361
• Updates the date.