prepare for 0.5.1 release #302
Merged
Conversation
This file contains 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
mwear
requested review from
bai,
dazuma,
elskwid,
fbogsany and
luvtechno
as code owners
|
|
mwear
force-pushed
the
release_api_v0.5.1
branch
from
3808098 to
2c38519
Compare
fbogsany
approved these changes
Jul 21, 2020
|
Thanks @mwear ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR bumps the API and SDK versions and adds changelog entires in preparation for a patch release that will address #298 and #300. After this merges I can cut a new gem versions for opentelemetry-api and opentelemetry-sdk.