Release v0.32.0 on Sep 21, 2022

[haarchri]

Checklist

• Create the new release branch with minor version, i.e. release-0.21 for v0.21.0.
  • You can use the existing branch for patch releases.
• Tag release by running Tag action in Github UI against release branch, i.e. release-X branch.
  • Use v-prefixed version, like v0.21.0, for both description and tag.
• Run CI action against release branch.
• Tag the next pre-release by running Tag action in Github UI against master branch, if it's not a patch release.
  • The tag should be v0.22.0-rc.0 if you're releasing v0.21.x.
• Validate that you can install the published version, basic sanity check.
• Run Promote action to promote it in alpha channel if it's pre-1.0.
• Use Github UI to generate release notes.
  • Make sure to scan all PRs marked with breaking-change and add instructions for users to handle them.
• Create the next release issue with a title that has its date, 4 weeks after the current release day.
• Announce in Slack, Twitter etc.

[haarchri]

we will hold the release - for #1487

[mrcheese123]

@haarchri In #1487 you commented that the pull request was going to be held for the v0.33.0 release. Are you going ahead with the v0.32.0 release or are you skipping this release?

[haarchri]

We waiting die decission - If we want merge in v0.32.0 we will inform shortly

[haarchri]

we will start the release workflow now

[haarchri]

basic santitiy check done!

NAME                                                           HEALTHY   REVISION   IMAGE                                       STATE      DEP-FOUND   DEP-INSTALLED   AGE
providerrevision.pkg.crossplane.io/provider-aws-245ce7fb587d   True      2          docker.io/crossplane/provider-aws:v0.32.0   Active                                 12m