fix: force new release-please PR #3098
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
pkg:instrumentation-undici
pkg:instrumentation-kafkajs
pkg-status:unmaintained
maryliag
reviewed
Sep 24, 2025
maryliag
reviewed
Sep 24, 2025
maryliag
reviewed
Sep 24, 2025
maryliag
reviewed
Sep 24, 2025
Co-authored-by: Marylia Gutierrez <maryliag@gmail.com>
Co-authored-by: Marylia Gutierrez <maryliag@gmail.com>
Co-authored-by: Marylia Gutierrez <maryliag@gmail.com>
JamieDanielson
approved these changes
Sep 24, 2025
This was referenced Sep 24, 2025
Closed
Closed
Closed
Merged
trentm
added a commit
to trentm/opentelemetry-js-contrib
that referenced
this pull request
Sep 26, 2025
This reverts commit 13c58e9.
trentm
added a commit
to trentm/opentelemetry-js-contrib
that referenced
this pull request
Sep 29, 2025
This reverts commit 13c58e9 (open-telemetry#3098), as an easy way to make an innocuous change to every package to force a new release of all packages now that the release process has been successfully updated to use npm Trusted Publishers (OIDC-based auth for publishing).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
We published GitHub releases, but did not publish to NPM due to an error in the release workflow that was resolved with #3096
This PR is to force a new release-please PR by making a change in one file for each package.
I chose
README.mdfor this since it does not have any impact on functionality, but every package has one. I updated the npm badges on eachREADME.mdto point towards the same site that we already use for the license image. I added the badges in theREADME.md's where they were missing.Edit: It's a silly change - but there needs to be a change in each package and it was the change with the lowest impact I could think of.