@@ -70,17 +70,17 @@ If (and only if) you're creating a release `vx.y.0` (i.e. a minor release):
7070 the actual remote name for the upstream source (not your private fork).
7171
7272- Setup the CI for the new branch in the prow configuration.
73- [ Prior art] ( https://github.com/metal3-io/project-infra/pull/976 )
73+ [ Prior art] ( https://github.com/metal3-io/project-infra/pull/1237 )
7474
7575Create a development branch (e.g. ` prepare-x.y ` ) from the newly created branch:
7676
7777- Pin the constraints.
78- [ Prior art] ( https://github.com/metal3-io/ironic-image/pull/655 ) .
78+ [ Prior art] ( https://github.com/metal3-io/ironic-image/pull/900 )
7979
8080- Pin the ` IRONIC_SOURCE ` to specific SHA in the upstream release branch. It must
8181 be in format ` ARG IRONIC_SOURCE=<sha> # <branch_name> ` for Renovate bot to
8282 be able to update it automatically in the future.
83- [ Prior art] ( https://github.com/metal3-io/ironic-image/pull/771 )
83+ [ Prior art] ( https://github.com/metal3-io/ironic-image/pull/900 )
8484
8585- Commit your changes, push the new branch and create a pull request:
8686 - The commit and PR title should be
@@ -189,7 +189,8 @@ If project dependencies have changed, then copy the configuration of `main`,
189189and adjust the ` ignore ` rules to match release branches. As generic rule we
190190don't allow major or minor bumps in release branches.
191191
192- [ Prior art] ( https://github.com/metal3-io/ironic-image/pull/702 )
192+ Prior art: See the PR that added release-34.0 to dependabot configuration
193+ (this change will be the reference once committed).
193194
194195### Renovate configuration
195196
@@ -199,11 +200,14 @@ updated in the `main` branch to include the new release branch.
199200
200201Update ` renovate.json ` in ` main ` branch:
201202
202- - Add the new release branch (e.g., ` release-32 .0 ` ) to the ` baseBranchPatterns `
203+ - Add the new release branch (e.g., ` release-34 .0 ` ) to the ` baseBranchPatterns `
203204 array
204205- Add the new release branch to the ` packageRules ` section with the daily
205206 schedule configuration matching other release branches
206207
208+ Prior art: See the PR that added release-34.0 to renovate configuration
209+ (this change will be the reference once committed).
210+
207211### Branch protection rules
208212
209213Branch protection rules need to be applied to the new release branch. Copy the
@@ -231,12 +235,12 @@ Update the [user guide](https://github.com/metal3-io/metal3-docs/tree/main/docs/
231235 in older ironic-image branches.
232236
233237- Update ` README.md ` with release specific information, both on ` main ` and in the
234- new ` release-X.Y ` branch as necessary.
238+ new ` release-X.Y ` branch as necessary (if applicable) .
235239 [ Prior art] ( https://github.com/metal3-io/ironic-image/pull/594 )
236240
237241- In the ` release-X.Y ` branch, update the build badges in the ` README.md ` to point
238242 to correct Jenkins jobs, so the build statuses of the release branch are
239- visible.
243+ visible (if applicable) .
240244 [ Prior art] ( https://github.com/metal3-io/ironic-image/pull/595 )
241245
242246### Update milestones
@@ -249,7 +253,7 @@ Update the [user guide](https://github.com/metal3-io/metal3-docs/tree/main/docs/
249253
250254Milestones must also be updated in the Prow configuration.
251255
252- [ Prior art] ( https://github.com/metal3-io/project-infra/pull/976 ) .
256+ [ Prior art] ( https://github.com/metal3-io/project-infra/pull/1237 )
253257
254258## Ironic Standalone Operator updates
255259
0 commit comments