open-telemetry/opentelemetry-ruby-contrib
Improve Initial Gem Release Process
オープン
#1,373 opened on 2025/01/29
help wantedkeep
Repository metrics
- Stars
- (135 個のスター)
- PR merge metrics
- (PR metrics pending)
説明
We tend to have the same mistakes repeated when releasing new gems. I think we need a linter or guide to help us avoid them in the future.
Our automated release tooling handles versioning. For initial releases this should have been set to
0.0.0The instrumentation generator seeds the version here:
That along with the empty CHANGELOG signals to the release tooling that this specific version will need to be an "initial release" of the gem https://github.com/open-telemetry/opentelemetry-ruby-contrib/blob/main/.instrumentation_generator/templates/CHANGELOG.md.tt
Originally posted by @arielvalentin in https://github.com/open-telemetry/opentelemetry-ruby-contrib/pull/1313#discussion_r1933999091