|
2 | 2 |
|
3 | 3 | ## Preparing a new major or minor release
|
4 | 4 |
|
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). |
6 | 6 | * Press the "Run workflow" button, and leave the default branch `main` selected.
|
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`.
|
|
13 | 13 | ## Preparing a new patch release
|
14 | 14 |
|
15 | 15 | * 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). |
17 | 17 | * Press the "Run workflow" button, then select the release branch from the dropdown list,
|
18 | 18 | e.g. `release/v1.9.x`, then enter the pull request number that you want to backport,
|
19 | 19 | then click the "Run workflow" button below that.
|
20 | 20 | * Review and merge the backport pull request that it generates.
|
21 | 21 | * Merge a pull request to the release branch updating the `CHANGELOG.md`.
|
22 | 22 | * 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). |
24 | 24 | * Press the "Run workflow" button, then select the release branch from the dropdown list,
|
25 | 25 | e.g. `release/v1.9.x`, and click the "Run workflow" button below that.
|
26 | 26 | * Review and merge the pull request that it creates for updating the version.
|
27 | 27 |
|
28 | 28 | ## Making the release
|
29 | 29 |
|
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). |
31 | 31 | * Press the "Run workflow" button, then select the release branch from the dropdown list,
|
32 | 32 | e.g. `release/v1.9.x`, and click the "Run workflow" button below that.
|
33 | 33 | * This workflow will publish the artifacts and publish a GitHub release with release notes based on the change log.
|
|
69 | 69 | ## After the release
|
70 | 70 |
|
71 | 71 | * 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 |
75 | 75 | * If for some reason the action failed, see [Publish failed](#publish-failed) below
|
76 | 76 | * Move stable tag
|
77 | 77 | * Run the following (TODO automate):
|
|
0 commit comments