v1.31.0

What's Changed

• RUNTIME UPGRADE: go runtime go1.24.0 → go1.25.7 [tests/integration_tests/helloV2] by @campaigner-prod[bot] in #225
• RUNTIME UPGRADE: go runtime go1.24.0 → go1.25.7 [tests/integration_tests/error] by @campaigner-prod[bot] in #226
• DEPENDENCY UPGRADE: minor: github.com/DataDog/datadog-lambda-go, github.com/aws/aws-lambda-go · patch: gopkg.in/DataDog/dd-trace-go.v1 [tests/integration_tests] by @campaigner-prod[bot] in #229
• chore: add note to migration instructions in new datadog-lambda-go readme by @happynancee in #230
• Start tracer while initializing trace lambda listener by @shreyamalpani in #222

New Contributors

• @campaigner-prod[bot] made their first contribution in #225
• @shreyamalpani made their first contribution in #222

Full Changelog: v1.30.0...v1.31.0

v1.30.0

What's Changed

• Add request-id as header to start/end invocation. by @purple4reina in #220
• chore: deprecation notice by @joeyzhao2018 in #221

Full Changelog: v1.29.0...v1.30.0

v1.29.0

• support multivalue headers
• include datadog origin header in trace context

Full Changelog: v1.28.0...v1.29.0

v1.28.0

What's Changed

• Properly handle go runtime versions containing a comma. by @purple4reina in #214

Full Changelog: v1.27.0...v1.28.0

v1.27.0

What's Changed

Important

datadog-lambda-go v1.27.0 uses dd-trace-go v1.74.6
dd-trace-go v1.74 is different from <1.73 as it serves as a transitional version for dd-trace-go v2.
You can now use dd-trace-go v2 for any of your custom instrumentations as v1.74.6 should be forward compatible.
We are still working on fully adapting to dd-trace-go v2 for datadog-lambda-go.

Full Changelog: v1.26.0...v1.27.0

v1.26.0

What's Changed

• fix: read full response body and close connections to avoid file desc… by @astuyve in #209

Full Changelog: v1.25.1...v1.26.0

v1.25.1

What's Changed

• Revert calling tracer.Stop after each invocation. by @purple4reina in #208

Full Changelog: v1.25.0...v1.25.1

v1.25.0

Warning

There is a known bug in this release that prevents all traces after the first invocation from being sent to intake. If your functions require Datadog Tracing, please revert to v1.24.0

What's Changed

• fix: stop the tracer after each invocation. Disable telemetry by @astuyve in #207

New Contributors

• @astuyve made their first contribution in #207

Full Changelog: v1.24.0...v1.25.0

v1.24.0

What's Changed

• Fix comment for OTEL env var reading condition by @sudame in #200
• fix: problem getting the sampling priority by @joeyzhao2018 in #205

New Contributors

• @sudame made their first contribution in #200

Full Changelog: v1.23.0...v1.24.0

v1.23.0

What's Changed

• Use FIPS endpoint when decrypting KMS key if in Govcloud region by @nhulston in #196
  • This was actually modified in the following commit to be based on the DD_LAMBDA_FIPS_MODE flag which defaults to true in govcloud.
• feat: DD_LAMBDA_FIPS_MODE handling for metrics by @apiarian-datadog in #199

Breaking Change

WIth FIPS mode enabled we can no longer ship metrics directly to the Datadog API. Please use the datadog-lambda-extension or the Datadog Forwarder. FIPS mode is enabled by default in GovCloud and can be configured with the DD_LAMBDA_FIPS_MODE environment variable or the new FIPSMode config field.

New Contributors

• @apiarian-datadog made their first contribution in #199

Full Changelog: v1.22.0...v1.23.0