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?
I'm following along the checklist at
https://github.com/DataDog/libdatadog/blob/main/ruby/README.md#releasing-a-new-version-to-rubygemsorg.
Motivation
Use latest release for Ruby profiling.
How to test the change?
I've gone ahead and updated the Ruby profiler to use this version in https://github.com/DataDog/dd-trace-rb/tree/ivoanjo/upgrade-to-libdatadog-0.8.0 . I am able to run the Ruby profiler test suite both on macOS as well as on Linux with the new release.
To reproduce my results, you need to do the following:
cd ruby && bundle exec rake package
ruby/pkg/libdatadog-0.8.0.1.0.gem
that is generated by packaging to the root of the dd-trace-rb repositorydocker-compose run --rm tracer-2.7 /bin/bash
gem install libdatadog-0.8.0.1.0.gem
bundle install
bundle exec rake clean compile && bundle exec rspec spec/datadog/profiling