Skip to content

bump minor version to 3.29.0#154

Draft
zarirhamza wants to merge 1 commit into
mainfrom
zarir.hamza/release-v3.29.0
Draft

bump minor version to 3.29.0#154
zarirhamza wants to merge 1 commit into
mainfrom
zarir.hamza/release-v3.29.0

Conversation

@zarirhamza
Copy link
Copy Markdown
Contributor

What does this PR do?

Release bump from v3.28.0 to v3.29.0. This release packages up the AppSec FFI fix merged in #153.

Notable changes since v3.28.0:

  • fix: compile FFI from source using the AWS Lambda image (Compile FFI from source using AWS Lambda image #153) — switches the layer build from ruby:X.Y (Debian) to public.ecr.aws/lambda/ruby:X.Y so native extensions compile against Lambda's actual glibc / libffi. After the datadog gem install, the precompiled FFI gem (which is missing the Ruby 3.2 ABI for ffi_c) is uninstalled and reinstalled from source. Fixes the cold-start LoadError: cannot load such file -- ffi_c crash that hit Ruby 3.2 functions whenever DD_APPSEC_ENABLED=true was set.

Motivation

Cuts a release so the AppSec-fixed Datadog-Ruby3-2 / Datadog-Ruby3-4 / Datadog-Ruby4-0 (and -ARM variants) layers get published, which in turn unblocks the (ruby32, appsec_tracer) scenarios currently xfailed in serverless-e2e-tests.

Testing Guidelines

Per the Lambda Layer Ruby runbook: once this PR's gitlab pipeline finishes its build layer / check layer size / unit test / integration test jobs, the publish layer sandbox jobs are manual — clicking those will publish test layers to the serverless-sandbox AWS account (425362996713) for verification.

Plan:

  1. Wait for build + integration tests to pass.
  2. Manually trigger the publish layer sandbox jobs to get test layer ARNs.
  3. Verify the AppSec fix locally with the sandbox layer ARN before merging.
  4. After step 3 is green: merge, tag v3.29.0, push tag, click the prod signing + publish jobs per runbook.

Additional Notes

Diff is a single-line minor bump of MINOR = 28MINOR = 29 in lib/datadog/lambda/version.rb. No code or test changes — 2f51619 (the merge of #153) is already on main.

Types of changes

  • Bug fix
  • New feature
  • Breaking change
  • Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

  • This PR's description is comprehensive
  • This PR contains breaking changes that are documented in the description
  • This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
  • This PR impacts documentation, and it has been updated (or a ticket has been logged)
  • This PR's changes are covered by the automated tests
  • This PR collects user input/sensitive content into Datadog

@zarirhamza zarirhamza requested review from a team as code owners May 20, 2026 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants