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: docs/release.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -99,7 +99,7 @@ The last step of the release process creates artifacts for the new version of th
99
99
1. Run the GitHub Action workflow "Update Version in Distributions and Prepare PR" which will update the minor version automatically (e.g. v0.116.0 -> v0.117.0) or manually provide a new version if releasing a bugfix or skipping a version. Select "create pr" option.
100
100
- 🛑 **Do not move forward until this PR is merged.** 🛑
101
101
102
-
2. Check out main and ensure it has the "Prepare release" commit in your local
102
+
2. Check out main and ensure it has the "Update version from ..." commit in your local
103
103
copy by pulling in the latest from
104
104
`open-telemetry/opentelemetry-collector-releases`. Assuming your upstream
105
105
remote is named `upstream`, you can try running:
@@ -220,7 +220,6 @@ Once a module is ready to be released under the `1.x` version scheme, file a PR
0 commit comments