Prepare for 1.0-rc.3 release#456
Merged
codeboten merged 6 commits intoopen-telemetry:mainfrom Dec 11, 2025
Merged
Conversation
Closed
Member
Author
|
This is ready to go from my perspective. Will wait for a couple of approvals because I'm hoping this is the last RC. |
Member
Author
|
@open-telemetry/configuration-approvers please take a look! |
Member
Author
|
Will wait for one more approval before merging and cutting the release |
Member
Author
|
|
Member
Author
|
FYI, we've updated the java implementation to the latest ref on main here: open-telemetry/opentelemetry-java#7861 Things look good from our side. |
MrAlias
approved these changes
Dec 11, 2025
Member
|
This PR is now merged, but the actual release with a v1.0.0-rc3 label is missing. |
Member
Author
|
Working on it! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Couple of straggler PRs we should get resolved:- #433 not important for stability, but seems reasonable and there is strong interest- #445 or #449 to decide on standard case for enum values- #446 not strictly necessary but won't be able to do it later- #450 easy and uncontroversial- #451 nice to have for better compiled descriptions