Skip to content

Commit b701980

Browse files
authored
rel (#1700)
1 parent c5a2db5 commit b701980

File tree

3 files changed

+8
-8
lines changed

3 files changed

+8
-8
lines changed

.github/workflows/release.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ jobs:
125125
--title "Version ${STABLE_VERSION}/${UNSTABLE_VERSION}" \
126126
--notes-file /tmp/release-notes.txt \
127127
--discussion-category announcements \
128-
v$STABLE_VERSION
128+
v$UNSTABLE_VERSION
129129
130130
- uses: actions/checkout@v3
131131
with:

RELEASING.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
## Preparing a new major or minor release
44

5-
* Run the [Prepare release branch workflow](https://github.com/open-telemetry/opentelemetry-python/actions/workflows/prepare-release-branch.yml).
5+
* Run the [Prepare release branch workflow](https://github.com/open-telemetry/opentelemetry-python-contrib/actions/workflows/prepare-release-branch.yml).
66
* Press the "Run workflow" button, and leave the default branch `main` selected.
77
* If making a pre-release of stable components (e.g. release candidate),
88
enter the pre-release version number, e.g. `1.9.0rc2`.
@@ -13,21 +13,21 @@
1313
## Preparing a new patch release
1414

1515
* Backport pull request(s) to the release branch.
16-
* Run the [Backport workflow](https://github.com/open-telemetry/opentelemetry-python/actions/workflows/backport.yml).
16+
* Run the [Backport workflow](https://github.com/open-telemetry/opentelemetry-python-contrib/actions/workflows/backport.yml).
1717
* Press the "Run workflow" button, then select the release branch from the dropdown list,
1818
e.g. `release/v1.9.x`, then enter the pull request number that you want to backport,
1919
then click the "Run workflow" button below that.
2020
* Review and merge the backport pull request that it generates.
2121
* Merge a pull request to the release branch updating the `CHANGELOG.md`.
2222
* The heading for the unreleased entries should be `## Unreleased`.
23-
* Run the [Prepare patch release workflow](https://github.com/open-telemetry/opentelemetry-python/actions/workflows/prepare-patch-release.yml).
23+
* Run the [Prepare patch release workflow](https://github.com/open-telemetry/opentelemetry-python-contrib/actions/workflows/prepare-patch-release.yml).
2424
* Press the "Run workflow" button, then select the release branch from the dropdown list,
2525
e.g. `release/v1.9.x`, and click the "Run workflow" button below that.
2626
* Review and merge the pull request that it creates for updating the version.
2727

2828
## Making the release
2929

30-
* Run the [Release workflow](https://github.com/open-telemetry/opentelemetry-python/actions/workflows/release.yml).
30+
* Run the [Release workflow](https://github.com/open-telemetry/opentelemetry-python-contrib/actions/workflows/release.yml).
3131
* Press the "Run workflow" button, then select the release branch from the dropdown list,
3232
e.g. `release/v1.9.x`, and click the "Run workflow" button below that.
3333
* This workflow will publish the artifacts and publish a GitHub release with release notes based on the change log.
@@ -69,9 +69,9 @@
6969
## After the release
7070

7171
* Check PyPI
72-
* This should be handled automatically on release by the [publish action](https://github.com/open-telemetry/opentelemetry-python/blob/main/.github/workflows/publish.yml).
73-
* Check the [action logs](https://github.com/open-telemetry/opentelemetry-python/actions?query=workflow%3APublish) to make sure packages have been uploaded to PyPI
74-
* Check the release history (e.g. https://pypi.org/project/opentelemetry-api/#history) on PyPI
72+
* This should be handled automatically on release by the [publish action](https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/.github/workflows/release.yml).
73+
* Check the [action logs](https://github.com/open-telemetry/opentelemetry-python-contrib/actions/workflows/release.yml) to make sure packages have been uploaded to PyPI
74+
* Check the release history (e.g. https://pypi.org/project/opentelemetry-instrumentation/#history) on PyPI
7575
* If for some reason the action failed, see [Publish failed](#publish-failed) below
7676
* Move stable tag
7777
* Run the following (TODO automate):

0 commit comments

Comments
 (0)