●Change8

Migrating to New Relic SDK v13.0.0

Version v13.0.0 introduces 1 breaking change. This guide details how to update your code.

Released: 5/12/2026

1
Breaking Changes
2
Migration Steps
4
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

WebTransaction_GCDataSource.record_gcAsyncGeneratorProxystarlette.StreamingResponse

Breaking Changes

●Issue #1

Support for Python lambda functions in the configuration file (used for dynamically naming various traces and methods) has been removed due to security vulnerabilities. Users must now use static values or other supported configuration methods instead of lambdas for naming.

Migration Steps

  1. 1
    If you were using Python lambda functions in your configuration file for naming traces or methods, replace them with static configuration values.
  2. 2
    Update code references from `response.status` to use `http.statusCode` to prepare for its removal in version 14.0.0.

Release Summary

This release removes support for Python lambda functions in configuration for security reasons and introduces several new features, including Anthropic and Gemini streaming instrumentation, and default exclusion of the `newrelic` header. Several bugs related to context propagation and reconnect logic have also been fixed.

Need More Details?

View the full release notes and all changes for New Relic SDK v13.0.0.

View Full Changelog