Skip to content

Commit ba5496a

Browse files
authored
Update RELEASING.md (#4596)
1 parent e17c397 commit ba5496a

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

RELEASING.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,13 +22,16 @@
2222
* Press the "Run workflow" button, then select the release branch from the dropdown list,
2323
e.g. `release/v1.9.x`, then enter the pull request number that you want to backport,
2424
then click the "Run workflow" button below that.
25+
* Add the label `backport` to the generated pull request.
26+
* In case label automation doesn't work, just close and reopen the PR so that the workflow will take into account the label automation we have in place.
2527
* Review and merge the backport pull request that it generates.
2628
* Merge a pull request to the release branch updating the `CHANGELOG.md`.
2729
* The heading for the unreleased entries should be `## Unreleased`.
2830
* Run the [Prepare patch release workflow](https://github.com/open-telemetry/opentelemetry-python/actions/workflows/prepare-patch-release.yml).
2931
* Press the "Run workflow" button, then select the release branch from the dropdown list,
3032
e.g. `release/v1.9.x`, and click the "Run workflow" button below that.
3133
* Review and merge the pull request that it creates for updating the version.
34+
* Note: If you are doing a patch release in `-core` repo, you should also do an equivalent patch release in `-contrib` repo (even if there's no fix to release), otherwise tests in CI will fail.
3235

3336
## Making the release
3437

0 commit comments

Comments
 (0)