You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASING.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,9 +9,8 @@
9
9
(otherwise the workflow will pick up the version from `main` and just remove the `.dev` suffix).
10
10
* Review the two pull requests that it creates.
11
11
(one is targeted to the release branch and one is targeted to `main`).
12
-
* The builds will fail for both the `main` and release pr because of validation rules. Follow the [release workflow](https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/RELEASING.md) for the contrib repo up until this same point.
13
-
* Change the CONTRIB_REPO_SHA of core PRs to point to their counterpart in contrib.
14
-
* Change the CORE_REPO_SHA of contrib PRs to point to their counterpart in core.
12
+
* The builds will fail for the release PR because of validation rules. Follow the [release workflow](https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/RELEASING.md) for the contrib repo up until this same point.
13
+
* Close and reopen the PR so that the workflow will take into account the label automation we have in place
15
14
* Release builds now should pass.
16
15
* Merge the release PR.
17
16
* Merge the PR to main (this can be done separately from [making the release](#making-the-release))
@@ -23,13 +22,16 @@
23
22
* Press the "Run workflow" button, then select the release branch from the dropdown list,
24
23
e.g. `release/v1.9.x`, then enter the pull request number that you want to backport,
25
24
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.
26
27
* Review and merge the backport pull request that it generates.
27
28
* Merge a pull request to the release branch updating the `CHANGELOG.md`.
28
29
* The heading for the unreleased entries should be `## Unreleased`.
29
30
* Run the [Prepare patch release workflow](https://github.com/open-telemetry/opentelemetry-python/actions/workflows/prepare-patch-release.yml).
30
31
* Press the "Run workflow" button, then select the release branch from the dropdown list,
31
32
e.g. `release/v1.9.x`, and click the "Run workflow" button below that.
32
33
* 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.
0 commit comments