Read OpenTelemetry project contributing guide for general information about the project.
- Docker
If there is a CHANGELOG.md
file in the component you are updating,
please make sure to add an entry for your change in the "Unreleased" section.
- Add new desired version number in all
CHANGELOG.md
files (instead of "Unreleased") and ensure no (relevant) entries are missing- This currently applies to semantic-conventions/CHANGELOG.md and schemas/CHANGELOG.md.
- Create the release at https://github.com/open-telemetry/build-tools/releases/new
- Tag:
v0.xx.y
- Title:
Release version 0.xx.y
- Click on Generate release notes
- Structure release notes with the headings used in former release notes (since one release applies to multiple distinct components)
- Verify that the release looks like expected and hit Publish release
- Tag:
- Verify the release
- Ensure all workflows in https://github.com/open-telemetry/build-tools/actions succeeded (branch = the new version tag)
- Ensure all images were pushed to https://hub.docker.com/u/otel as expected. Currently these are:
- Update the respective version references in the https://github.com/open-telemetry/opentelemetry-specification repository, if needed