Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release: Release 11 gems #1464

Closed
wants to merge 1 commit into from
Closed

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jun 8, 2023

This pull request prepares new gem releases for the following gems:

  • opentelemetry-api 2.0.0 (was 1.1.0)
  • opentelemetry-registry 0.3.0 (was 0.2.0)
  • opentelemetry-sdk 2.0.0 (was 1.2.1)
  • opentelemetry-sdk-experimental 0.3.0 (was 0.2.0)
  • opentelemetry-common 0.20.0 (was 0.19.7)
  • opentelemetry-exporter-jaeger 0.23.0 (was 0.22.0)
  • opentelemetry-exporter-zipkin 0.23.0 (was 0.22.0)
  • opentelemetry-propagator-b3 0.21.0 (was 0.20.0)
  • opentelemetry-propagator-jaeger 0.21.0 (was 0.20.0)
  • opentelemetry-semantic_conventions 2.0.0 (was 1.10.0)
  • opentelemetry-test-helpers 0.4.0 (was 0.3.0)

For each gem, this pull request modifies the gem version and provides an initial changelog entry based on conventional commit messages. You can edit these changes before merging, to release a different version or to alter the changelog text.

  • To confirm this release, merge this pull request, ensuring the "release: pending" label is set. The release script will trigger automatically on merge.
  • To abort this release, close this pull request without merging.

The generated changelog entries have been copied below:


opentelemetry-api

v2.0.0 / 2023-06-08

  • BREAKING CHANGE: Remove support for EoL Ruby 2.7

  • ADDED: Remove support for EoL Ruby 2.7


opentelemetry-registry

v0.3.0 / 2023-06-08

  • BREAKING CHANGE: Remove support for EoL Ruby 2.7

  • ADDED: Remove support for EoL Ruby 2.7


opentelemetry-sdk

v2.0.0 / 2023-06-08

  • BREAKING CHANGE: Remove support for EoL Ruby 2.7

  • ADDED: Remove support for EoL Ruby 2.7

  • FIXED: SDK requires opentelemetry-common 0.19.7


opentelemetry-sdk-experimental

v0.3.0 / 2023-06-08

  • BREAKING CHANGE: Remove support for EoL Ruby 2.7

  • ADDED: Remove support for EoL Ruby 2.7


opentelemetry-common

v0.20.0 / 2023-06-08

  • BREAKING CHANGE: Remove support for EoL Ruby 2.7

  • ADDED: Remove support for EoL Ruby 2.7


opentelemetry-exporter-jaeger

v0.23.0 / 2023-06-08

  • BREAKING CHANGE: Remove support for EoL Ruby 2.7

  • ADDED: Remove support for EoL Ruby 2.7


opentelemetry-exporter-zipkin

v0.23.0 / 2023-06-08

  • BREAKING CHANGE: Remove support for EoL Ruby 2.7

  • ADDED: Remove support for EoL Ruby 2.7


opentelemetry-propagator-b3

v0.21.0 / 2023-06-08

  • BREAKING CHANGE: Remove support for EoL Ruby 2.7

  • ADDED: Remove support for EoL Ruby 2.7


opentelemetry-propagator-jaeger

v0.21.0 / 2023-06-08

  • BREAKING CHANGE: Remove support for EoL Ruby 2.7

  • ADDED: Remove support for EoL Ruby 2.7


opentelemetry-semantic_conventions

v2.0.0 / 2023-06-08

  • BREAKING CHANGE: Remove support for EoL Ruby 2.7

  • ADDED: Remove support for EoL Ruby 2.7


opentelemetry-test-helpers

v0.4.0 / 2023-06-08

  • BREAKING CHANGE: Remove support for EoL Ruby 2.7

  • ADDED: Remove support for EoL Ruby 2.7

@arielvalentin
Copy link
Contributor

@robertlaurin how does our versioning strategy map to the OTel Spec? Is there a secondary mapping to consider here as opposed to releasing a Major version of the API and SDK gems?

@robertlaurin
Copy link
Contributor

@robertlaurin how does our versioning strategy map to the OTel Spec? Is there a secondary mapping to consider here as opposed to releasing a Major version of the API and SDK gems?

This was the autogenerated stuff, I'm going to rewrite the versioning here so we're not doing major bumps to the API. I'll flag for a secondary review once I've cleaned it up.

@github-actions github-actions bot added release: aborted Automated release was aborted and removed release: pending Automated release is pending labels Jun 8, 2023
@github-actions github-actions bot deleted the release/multi/20230608174253 branch June 8, 2023 22:16
@github-actions
Copy link
Contributor Author

github-actions bot commented Jun 8, 2023

Release PR closed without merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release: aborted Automated release was aborted
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants