Release v0.27.0 on May 04, 2022

[haarchri]

Checklist

• Create the new release branch with minor version, i.e. release-0.27 for v0.27.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.27.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.28.0-rc.0 if you're releasing v0.27.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 have one blocking issue #1272

[ezgidemirel]

During the review of this PR, we identified another bug. It would be great if we can wait for the PR.

[haarchri]

since #1298 is fixed we will start with the release 0.27

[muvaf]

@haarchri Got back from the holiday break, do you want me to assign the issue to you?

[haarchri]

I currently publish the release ;) think will be finished next 30 min

[haarchri]

basic test is done

NAME                                                           HEALTHY   REVISION   IMAGE                             STATE    DEP-FOUND   DEP-INSTALLED   AGE
providerrevision.pkg.crossplane.io/provider-aws-866abfbb37fc   True      1          crossplane/provider-aws:v0.27.0   Active                               10m27s

NAME           INSTALLED   HEALTHY   PACKAGE                           AGE
provider-aws   True        True      crossplane/provider-aws:v0.27.0   10m58s

[muvaf]

@haarchri Thank you!!