generated from honeycombio/.github
-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
rel: prepare v1.3.0/v0.27.0-beta (#340)
## Which problem is this PR solving? - release of new main package, including dependency updates and method changes from OTel v1.4.0 - release of new instrumentation package, including name change ## Short description of the changes - add changelog entries. - We renamed `AutoInstrumentations` to `CommonInstrumentations`; see #327 for more details. - OTel changed to `AddOpenTelemetry().WithTracing` and `AddOpenTelemetry().WithMetrics`; see #334 for more details. - Update versions of main package from 1.2.1 to 1.3.0 - Update versions of instrumentation packages from 0.26.1-beta to 0.27.0-beta - Update releasing notes with extra details for clarity Once the release is out, docs updates can be merged in for public docs and in-app onboarding (see #339 )
- Loading branch information
1 parent
e083e55
commit 224ee26
Showing
8 changed files
with
47 additions
and
22 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,16 @@ | ||
# Releasing Process | ||
|
||
1. Update changelog | ||
2. Update VersionPrefix (and VersionSuffix if necessary) in the csproj file | ||
- If updating the OTel SDK, update the OTLP version in `HoneycombOptions.cs` | ||
3. Open a PR with the above, and merge that into main | ||
4. Tag the merged commit with the new version (e.g. `v0.10.0-alpha`) | ||
5. Push the tag upstream (this will kick off the release pipeline in CI) | ||
6. Once the CI is done, publish the GitHub draft release as pre-release through GitHub UI | ||
- Update `CHANGELOG.md` with the changes since the last release. Consider automating with a command such as these two: | ||
- `git log $(git describe --tags --abbrev=0)..HEAD --no-merges --oneline > new-in-this-release.log` | ||
- `git log --pretty='%C(green)%d%Creset- %s | [%an](https://github.com/)'` | ||
- Update VersionPrefix (and VersionSuffix if necessary) in the `*.csproj` files | ||
- If updating the OTel SDK, update the OTLP version in `HoneycombOptions.cs` | ||
- If updating the OTel SDK, update the OTel version in `README.md` | ||
- Commit changes, push, and open a release preparation pull request for review. | ||
- Once the pull request is merged, fetch the updated `main` branch. | ||
- Apply a tag for the new version on the merged commit (e.g. `git tag -a v1.3.0 -m "v1.3.0"`) | ||
- Note: We only tag the main package (even if changes were made to the instr packages) so the pipeline doesn't double-run | ||
- Push the tag upstream (this will kick off the release pipeline in CI) e.g. `git push origin v1.3.0` | ||
- Ensure that there is a draft GitHub release created as part of CI publish steps (this will also publish to Nuget). | ||
- Click "generate release notes" in Github for full changelog notes and any new contributors | ||
- Publish the Github draft release - if it is a prerelease (e.g. beta) click the prerelease checkbox. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters