[PROF-10208] Package libdatadog v11.0.0 for Ruby#544
Merged
Conversation
# What does this PR do? This PR includes the changes documented in the "Releasing a new version to rubygems.org" part of the README: https://github.com/datadog/libdatadog/tree/main/ruby#releasing-a-new-version-to-rubygemsorg The v11 version bump PR (#529) had already bumped the version itself, so I just needed to add the hashes. # Motivation Enable Ruby to use libdatadog v11.0.0. # Additional Notes N/A # How to test the change? I've tested this release locally using the changes in DataDog/dd-trace-rb#3799 . As a reminder, new libdatadog releases don't get automatically picked up by dd-trace-rb, so the PR that bumps the Ruby profiler will also test this release against all supported Ruby versions.
ekump
approved these changes
Jul 22, 2024
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #544 +/- ##
==========================================
- Coverage 70.50% 70.45% -0.05%
==========================================
Files 208 208
Lines 28397 28414 +17
==========================================
- Hits 20020 20019 -1
- Misses 8377 8395 +18
🚀 New features to boost your workflow:
|
BenchmarksThis comment was omitted because it was over 65536 characters.Please check the Gitlab Job logs to see its output. |
ekump
pushed a commit
that referenced
this pull request
Jul 22, 2024
# What does this PR do? This PR includes the changes documented in the "Releasing a new version to rubygems.org" part of the README: https://github.com/datadog/libdatadog/tree/main/ruby#releasing-a-new-version-to-rubygemsorg The v11 version bump PR (#529) had already bumped the version itself, so I just needed to add the hashes. # Motivation Enable Ruby to use libdatadog v11.0.0. # Additional Notes N/A # How to test the change? I've tested this release locally using the changes in DataDog/dd-trace-rb#3799 . As a reminder, new libdatadog releases don't get automatically picked up by dd-trace-rb, so the PR that bumps the Ruby profiler will also test this release against all supported Ruby versions.
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
3 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.
What does this PR do?
This PR includes the changes documented in the "Releasing a new version to rubygems.org" part of the README:
https://github.com/datadog/libdatadog/tree/main/ruby#releasing-a-new-version-to-rubygemsorg
The v11 version bump PR (#529) had already bumped the version itself, so I just needed to add the hashes.
Motivation
Enable Ruby to use libdatadog v11.0.0.
Additional Notes
N/A
How to test the change?
I've tested this release locally using the changes in DataDog/dd-trace-rb#3799 .
As a reminder, new libdatadog releases don't get automatically picked up by dd-trace-rb, so the PR that bumps the Ruby profiler will also test this release against all supported Ruby versions.