1.5 KiB
1.5 KiB
Making a Release
- Ensure the referenced specification version is up to date. Use tooling to update the spec if needed.
- Run opentelemetry.io workflow
against
semantic-conventionssubmodule as a smoke-test for docs. Fix broken links, if any. - Create a staging branch for the release.
- Update
schema-next.yamlfile and move toschemas/{version}- Ensure the
nextversion is appropriately configured as the{version}. - Copy
schema-next.yamltoschemas/{version}. - Add
nextas a version inschema-next.yamlversion.
- Ensure the
- Run
make chlog-update VERSION=v{version}make chlog-updatewill clean up all the current.yamlfiles inside the.chloggenfolder automatically- Double check that
CHANGELOG.mdis updated with the properv{version}
- Send staging branch as PR for review.
- Update
- After the release PR is merged, create a new release:
- Set title and tag to
v{version} - Set target to the commit of the merged release PR
- Copy changelog to the release notes
- Verify that the release looks like expected
- Publish release
- Set title and tag to
New release is then auto-discovered by opentelemetry.io pipelines which (via bot-generated PR) eventually results in new version of schema file being published.