-
Notifications
You must be signed in to change notification settings - Fork 255
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 PR #1791 failed with errors #1792
Comments
This is the same error we received in a recent release, #1765, but as far as I can tell, everything was released successfully despite this command failing. We didn't want to release the |
Had a small amount of time to look into this, where I left it is it looks like the toys gem is being optimistic when determining which gems to release https://github.com/dazuma/toys/blob/17ed449da8299f272b834470ff6b279a59e8070b/.toys/release/.lib/release_utils.rb#L436 At a glance This would explain the erroneous attempt to release opentelemetry-exporter-otlp (and subsequent 422 response from GitHub api) even though it only has files changed related to opentelemetry-exporter-otlp-metrics. iiuc, GitHub api returns a 422 if you try to release a tag that's already been released. |
👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the |
Since we've merged #1799, I'm going to close this issue. If we get another failure like this one, a new issue will open. Thanks, @ericmustin! |
A release job failed.
Release PR: #1791
Commit: baeda39
Release job completed with errors.
Failed to release opentelemetry-exporter-otlp 0.29.1:
Command failed with exit code 1: ["gh", "api", "repos/open-telemetry/opentelemetry-ruby/releases", "--input", "-", "-H", "Accept: application/vnd.github.v3+json"]
Successfully released opentelemetry-exporter-otlp-metrics 0.3.0
Successfully released opentelemetry-metrics-api 0.2.0
Successfully released opentelemetry-metrics-sdk 0.5.0
The text was updated successfully, but these errors were encountered: