Skip to content

Commit a85f773

Browse files
authored
[PROF-11306] Package libdatadog v16.0.1 for Ruby (#864)
**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 **Motivation:** Enable Ruby to use libdatadog v16.0.1. Of particular interest, this includes improvements to crashtracking and the managed string table needed by DataDog/dd-trace-rb#4331 . **Additional Notes:** N/A **How to test the change?** I've tested this release locally using the changes in DataDog/dd-trace-rb#4353 . 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.
1 parent b581706 commit a85f773

File tree

3 files changed

+9
-7
lines changed

3 files changed

+9
-7
lines changed

ruby/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Note: No Ruby needed to run this! It all runs inside docker :)
2929
Note: Publishing new releases to rubygems.org can only be done by Datadog employees.
3030

3131
1. [ ] Locate the new libdatadog release on GitHub: <https://github.com/datadog/libdatadog/releases>
32-
2. [ ] Update the `LIB_VERSION_TO_PACKAGE` and `LIB_GITHUB_RELEASES` sections of the `Rakefile` with the new version
32+
2. [ ] Update the `LIB_GITHUB_RELEASES` section of the `Rakefile` with the hashes from the new version
3333
3. [ ] Update the <lib/libdatadog/version.rb> file with the `LIB_VERSION` and `VERSION` to use
3434
4. [ ] Commit change, open PR, get it merged
3535
5. [ ] Release by running `docker-compose run push_to_rubygems`.

ruby/Rakefile

+7-5
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,9 @@ require "rubygems/package"
1111

1212
RSpec::Core::RakeTask.new(:spec)
1313

14-
LIB_VERSION_TO_PACKAGE = "14.3.1"
14+
# Note: When packaging rc releases and the like, you may need to set this differently from LIB_VERSION
15+
LIB_VERSION_TO_PACKAGE = Libdatadog::LIB_VERSION
16+
1517
unless LIB_VERSION_TO_PACKAGE.start_with?(Libdatadog::LIB_VERSION)
1618
raise "`LIB_VERSION_TO_PACKAGE` setting in <Rakefile> (#{LIB_VERSION_TO_PACKAGE}) does not match " \
1719
"`LIB_VERSION` setting in <lib/libdatadog/version.rb> (#{Libdatadog::LIB_VERSION})"
@@ -20,22 +22,22 @@ end
2022
LIB_GITHUB_RELEASES = [
2123
{
2224
file: "libdatadog-aarch64-alpine-linux-musl.tar.gz",
23-
sha256: "57f83aff275628bb1af89c22bb4bd696726daf2a9e09b6cd0d966b29e65a7ad6",
25+
sha256: "54416e4078fa9d923869ecae1a7b32e0c9ae0a47ab8c999812bb3b69cffb85bd",
2426
ruby_platform: "aarch64-linux-musl"
2527
},
2628
{
2729
file: "libdatadog-aarch64-unknown-linux-gnu.tar.gz",
28-
sha256: "36db8d50ccabb71571158ea13835c0f1d05d30b32135385f97c16343cfb6ddd4",
30+
sha256: "ad16283494d565a1877c76d4a8765f789ec2acb70b0597b4efe6e7a20e8b4f97",
2931
ruby_platform: "aarch64-linux"
3032
},
3133
{
3234
file: "libdatadog-x86_64-alpine-linux-musl.tar.gz",
33-
sha256: "2f61fd21cf2f8147743e414b4a8c77250a17be3aecc42a69ffe54f0a603d5c92",
35+
sha256: "384a50bb5013f6098b37da650f0fe9aa7c11f44780da971f8a4a35d2e342f00b",
3436
ruby_platform: "x86_64-linux-musl"
3537
},
3638
{
3739
file: "libdatadog-x86_64-unknown-linux-gnu.tar.gz",
38-
sha256: "f01f05600591063eba4faf388f54c155ab4e6302e5776c7855e3734955f7daf7",
40+
sha256: "6cea4ef4ecd4f40c1c69118bc1bb842c20782b710b838df3917d02eea7575a4e",
3941
ruby_platform: "x86_64-linux"
4042
}
4143
]

ruby/lib/libdatadog/version.rb

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
module Libdatadog
44
# Current libdatadog version
5-
LIB_VERSION = "14.3.1"
5+
LIB_VERSION = "16.0.1"
66

77
GEM_MAJOR_VERSION = "1"
88
GEM_MINOR_VERSION = "0"

0 commit comments

Comments
 (0)