Skip to content

Commit

Permalink
Merge pull request #34 from jbw976/renovate-runtime
Browse files Browse the repository at this point in the history
chore: update release steps to keep crossplane-runtime renovate config up to date
  • Loading branch information
jbw976 authored Dec 19, 2024
2 parents 5053579 + 04cc1d4 commit 1b1a404
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions .github/ISSUE_TEMPLATE/release.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ examples of each step, assuming release vX.Y.0 is being cut.
- [ ] Confirm that all security/critical dependency update PRs from Renovate are merged into `main`
- https://github.com/crossplane/crossplane-runtime/pulls?q=is%3Apr+is%3Aopen+label%3Aautomated
- [ ] Created the release branch using the [GitHub UI][create-branch].
- [ ] (On the **Main** Branch) Created and merged an empty commit with `git commit --allow-empty -s -m "Empty commit after release-X.Y"`
- [ ] (On the **Main** Branch) Created and merged a PR to add the new release branch to the `baseBranches` list in `.github/renovate.json5`.
- [ ] (On the **Main** Branch) Run the [Tag workflow][tag-workflow-runtime] with the release candidate tag for the next release `vX.Y+1.0-rc.0`. Message suggested, but not required: `Release candidate vX.Y+1.0-rc.0.`.
- [ ] (On the **Release** Branch) Run the [Tag workflow][tag-workflow-runtime] with the release candidate tag for the next release `vX.Y.0-rc.1` (assuming the latest rc tag for `vX.Y.0` is `vX.Y.0-rc.0`). Message suggested, but not required: `Release candidate vX.Y.0-rc.1.`.
- [ ] **[In Core Crossplane]:** Prepared the release branch `release-X.Y`:
Expand Down Expand Up @@ -56,8 +56,10 @@ examples of each step, assuming release vX.Y.0 is being cut.
- [ ] Opened a [docs release issue]
- [ ] Checked that the [GitHub milestone] for this release only contains closed issues.
- [ ] Cut a Crossplane Runtime version and consume it from Crossplane.
- [ ] **[In Crossplane Runtime]**: Run the [Tag workflow][tag-workflow-runtime] on the `release-X.Y` branch with the proper release version, `vX.Y.0`. Message suggested, but not required: `Release vX.Y.0`.
- [ ] Published a [new release][new runtime release] for the tagged version, with the same name as the version, taking care of generating the changes list selecting as "Previous tag" `vX.<Y-1>.0`, so the first of the releases for the previous minor.
- [ ] **[In Crossplane Runtime]**:
- [ ] Run the [Tag workflow][tag-workflow-runtime] on the `release-X.Y` branch with the proper release version, `vX.Y.0`. Message suggested, but not required: `Release vX.Y.0`.
- [ ] Published a [new release][new runtime release] for the tagged version, with the same name as the version, taking care of generating the changes list selecting as "Previous tag" `vX.<Y-1>.0`, so the first of the releases for the previous minor.
- [ ] Update the `baseBranches` list in `.github/renovate.json5` on `main`, removing the now old unsupported release.
- [ ] **[In Core Crossplane]:** (On the **Release** Branch) Update the Crossplane Runtime dependency to `vX.Y.0`.
- [ ] (On the **Release** Branch) Run the [Tag workflow][tag-workflow] with the proper release version, `vX.Y.0`. Message suggested, but not required: `Release vX.Y.0`.
- [ ] (On the **Release** Branch) Run the [CI workflow][ci-workflow] and verified that the tagged build version exists on the [releases.crossplane.io] `build` channel, e.g. `build/release-X.Y/vX.Y.0/...` should contain all the relevant binaries.
Expand Down

0 comments on commit 1b1a404

Please sign in to comment.