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/crossplanevX.Y.0 has been released
according to the declared schedule, you should have:
[x] 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.
[x] Cut upbound/crossplanevX.Y.0-up.1 release from the release-X.Y branch by:
[x] 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.
[x] Running the CI workflow on the release-vX.Y branch to build and publish the latest tagged artifacts.
[x] You should now be able to run: docker pull upbound/crossplane:vX.Y.0-up.1
[x] 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:
[x] Update any reference to the old latest release to vX.Y.0-up.1, such as CROSSPLANE_TAG and CROSSPLANE_COMMIT in the Makefile.
[x] Run make helm.prepare to import any change to the templates in the upstream Helm chart.
[x] 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.
[x] Run make olm.build to generate the [OLM] bundle.
[x] Created the release-X.Y branch from main branch in UXP.
[x] Cut UXPvX.Y.0-up.1 release from the release-X.Y branch by:
[x] 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 candidate vX.Y.0-up.1.
[x] Running the CI workflow on the release-vX.Y branch to build and publish the latest tagged artifacts.
[x] Cut the next prerelease of UXP from the main branch, vX.<Y+1>.0-up.1-rc.1 by:
[x] 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.
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/crossplanevX.Y.0
has been released according to the declared schedule, you should have:release-vX.Y
release branch in upbound/crossplane, with upstream crossplane/crossplane release branch, up to thevX.Y.0
tag, adding any required change specific to the fork, see here for more details.vX.Y.0-up.1
release from therelease-X.Y
branch by: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
.release-vX.Y
branch to build and publish the latest tagged artifacts.docker pull upbound/crossplane:vX.Y.0-up.1
main
branch of upbound/universal-crossplane with the following changes, taking care to label it asbackport release-X.Y
:vX.Y.0-up.1
, such asCROSSPLANE_TAG
andCROSSPLANE_COMMIT
in theMakefile
.make helm.prepare
to import any change to the templates in the upstream Helm chart.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
.make olm.build
to generate the [OLM] bundle.release-X.Y
branch frommain
branch in UXP.vX.Y.0-up.1
release from therelease-X.Y
branch by:release-vX.Y
branch with the proper release version,vX.Y.0-up.1
. Message suggested but not required:Release candidate vX.Y.0-up.1
.release-vX.Y
branch to build and publish the latest tagged artifacts.main
branch,vX.<Y+1>.0-up.1-rc.1
by: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
.