@@ -51,7 +51,7 @@ Maintainers (admins) are needed to merge PRs and for the push to NuGet.**
5151 release] ( https://github.com/open-telemetry/opentelemetry-dotnet/actions/workflows/prepare-release.yml )
5252 workflow. Specify the ` tag-prefix ` and the ` version ` for the release. Make
5353 sure to run the workflow on the branch being released. This is typically
54- ` main ` but could be some other branch for hotfix (eg ` main-1.8 .0 ` ). The
54+ ` main ` but could be some other branch for hotfix (e.g. ` main-1.15 .0 ` ). The
5555 workflow will open a PR to update ` CHANGELOG.md ` files for the projects
5656 being released. If a stable version is specified as the ` version ` parameter,
5757 the workflow will also merge the contents of any detected
@@ -65,16 +65,16 @@ Maintainers (admins) are needed to merge PRs and for the push to NuGet.**
6565
6666 Run the PowerShell script `.\build\scripts\update-changelogs.ps1
6767 -minVerTagPrefix [ MinVerTagPrefix] -version [ Version] `. Where
68- ` [MinVerTagPrefix] ` is the tag prefix (eg ` core- ` ) for the components
69- being released and ` [Version] ` is the version being released (eg
70- ` 1.9 .0 ` ). This will update ` CHANGELOG.md ` files for the projects being
68+ ` [MinVerTagPrefix] ` is the tag prefix (e.g. ` core- ` ) for the components
69+ being released and ` [Version] ` is the version being released (e.g.
70+ ` 1.15 .0 ` ). This will update ` CHANGELOG.md ` files for the projects being
7171 released.
7272
7373 * ** Stable releases only** : Normalize PublicApi files
7474
7575 Run the PowerShell script `.\build\scripts\finalize-publicapi.ps1
7676 -minVerTagPrefix [ MinVerTagPrefix] ` . Where ` [ MinVerTagPrefix] ` is the tag
77- prefix (eg ` core- ` ) for the components being released. This will merge
77+ prefix (e.g. ` core- ` ) for the components being released. This will merge
7878 the contents of any detected ` PublicAPI.Unshipped.txt ` files in the
7979 ` .publicApi ` folder into the corresponding ` PublicAPI.Shipped.txt ` files
8080 for the projects being released.
@@ -116,16 +116,16 @@ Maintainers (admins) are needed to merge PRs and for the push to NuGet.**
116116 For example:
117117
118118 ```sh
119- git tag -a core-1.4.0-beta.1 -m "1.4.0-beta.1 of all core components"
120- git push origin core-1.4.0-beta.1
119+ git tag -a core-1.15.0 -m "core-1.15.0 of all core components"
120+ git push origin core-1.15.0
121121 ```
122122
123123 * If releasing core unstable components, push the tag prefixed with
124124 ` coreunstable- ` . For example:
125125
126126 ```sh
127- git tag -a coreunstable-1.9 .0-beta.1 -m "1.9 .0-beta.1 of all core unstable components"
128- git push origin coreunstable-1.9 .0-beta.1
127+ git tag -a coreunstable-1.15 .0-beta.1 -m "coreunstable-1.15 .0-beta.1 of all core unstable components"
128+ git push origin coreunstable-1.15 .0-beta.1
129129 ```
130130
131131 Pushing the tag will kick off the [ Build, pack, and publish to
@@ -204,14 +204,12 @@ Maintainers (admins) are needed to merge PRs and for the push to NuGet.**
204204 `Directory.Packages.props` to the just released stable version. Merge that
205205 PR once the build passes (this requires the packages be available on NuGet).
206206
207- 8. The [Complete
208- release](https://github.com/open-telemetry/opentelemetry-dotnet/actions/workflows/post-release.yml)
209- workflow should have invoked the [Core version
210- update](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/actions/workflows/core-version-update.yml)
211- workflow on the
212- [opentelemetry-dotnet-contrib](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/)
213- repository which opens a PR to update dependencies. Verify this PR was
214- opened successfully.
207+ 8. Manually run the [Core version update](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/actions/workflows/core-version-update.yml)
208+ workflow in the [opentelemetry-dotnet-contrib](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/)
209+ repository, which opens a PR to update dependencies. The tag that was created
210+ in step 5 should be used as the value of the `Release tag` input (for example
211+ `core-1.15.0` or `coreunstable-1.15.0-beta.1`). Verify this PR was opened successfully
212+ when the workflow completes.
215213
216214 9. For stable releases post an announcement in the [Slack
217215 channel](https://cloud-native.slack.com/archives/C01N3BC2W7Q) announcing the
0 commit comments