Skip to content

RELEASING.md

Latest commit

 

History

History
19 lines (17 loc) · 1.13 KB

RELEASING.md

File metadata and controls

19 lines (17 loc) · 1.13 KB

Releasing

  1. Prepare a draft release. Do not publish it yet.
  2. Run the opentelemetry.io workflow against the opentelemetry-specification submodule as a smoke test. Fix any broken links and confirm with the Communications SIG (#otel-comms). Re-confirm after any new PRs merge into the release PR.
  3. Update CHANGELOG.md:
    • Rename the existing Unreleased section to the new version (e.g. 1.50.0), removing any empty subsections.
    • Add a new Unreleased section at the top with empty subsections.
    • Verify no entries are missing or in the wrong section.
  4. Copy the changelog entries into the draft release description and un-draft it.
  5. Once approved, confirm the date in the CHANGELOG is current, then merge to create the release tag (e.g. v1.50.0).

The release is auto-discovered by opentelemetry.io pipelines, which will publish the new specification version via a bot-generated PR.