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
+3-1
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,10 @@
7
7
* If making a pre-release of stable components (e.g. release candidate),
8
8
enter the pre-release version number, e.g. `1.9.0rc2`.
9
9
(otherwise the workflow will pick up the version from `main` and just remove the `.dev` suffix).
10
-
* Review and merge the two pull requests that it creates
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
+
* Merge the one targeted towards the release branch.
13
+
* The builds will fail for the `main` pr because of validation rules. Follow the [release workflow](https://github.com/open-telemetry/opentelemetry-python/blob/main/RELEASING.md) for the core repo up until this same point. Change the SHAs of each PR to point at each other to get the `main` builds to pass.
0 commit comments