What pydantic/logfire shipped
Written by FoxPlug from the repository's own releases; not affiliated with Pydantic. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/pydantic/logfire; Pydantic did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of October 5, 2026
What shipped
- Version v6.0.0b8 shipped with support for OpenTelemetry 1.45, an optional compression setting with experimental zstd support, console attributes shown without verbose output, and FastAPI instrumentation that no longer produces duplicate telemetry. Release
- The client gained a compression option, with experimental zstd support that the ingest endpoints already handle, which helps with large spans. Pull request #2535
- Metric counters and histograms now honor an explicitly passed context instead of always using the active span. Pull request #2532
- The disk retryer no longer treats non-retryable responses such as a 401 as success, so queued exports are no longer silently dropped. Pull request #2529
- Raw-byte OTLP posts sent through the session request path now go through the normal retry handling and the disk retryer hand-off. Pull request #2503
- Integers below the int64 minimum are now converted to strings before export instead of being rejected by the encoder and dropped. Pull request #2502
- Fields declared with repr set to false are no longer exported or given nested schemas, matching how dataclasses already behaved. Pull request #2518
- Calling update name on a wrapped span now keeps the span message in sync with the new name. Pull request #2514
- HTTP span messages are now built from the stable HTTP semantic conventions as well as the older attribute names. Pull request #2516
- The command line interface now falls back to the environment base URL setting when no base URL argument is given. Pull request #2260
Why it matters
This week brings a new beta with support for a newer OpenTelemetry release and a compression option that helps with large spans, alongside fixes that keep telemetry complete. Several changes prevent silent data loss, including retries for raw byte exports, correct handling of very small integers, and not deleting queued exports after permanent errors. Issues with duplicate traces, metrics ignoring an explicit context, and spans whose message drifted from their name are also addressed, so the data reaching your backend is more accurate.
Changelog entry
- Release v6.0.0b8 with OpenTelemetry 1.45 support, console attributes without verbose output, compression with experimental zstd, and no duplicate FastAPI telemetry. Release
- Bump the version to v6.0.0b8. Pull request #2542
- Add a compression option and experimental zstd support for exports. Pull request #2535
- Route raw-byte OTLP posts through the existing retry path and disk retryer hand-off. Pull request #2503
- Record metric counters and histograms on an explicitly passed context. Pull request #2532
- Stop treating non-retryable disk retryer responses as success so queued exports are kept. Pull request #2529
- Skip attributes fields with repr set to false when exporting, matching dataclass behavior. Pull request #2518
- Convert span attribute integers below the int64 minimum to strings. Pull request #2502
- Build HTTP span messages from stable HTTP semantic conventions as well as the older names. Pull request #2516
- Keep the span message in sync with the name after update name. Pull request #2514
- Allow console attributes to be shown without verbose output. Pull request #2488
- Default the command line base URL to the environment base URL setting. Pull request #2260
V6.0.0b8 is out: OpenTelemetry 1.45 support, a compression option with experimental zstd, console attributes without verbose output, and no more duplicate FastAPI telemetry. We also fixed dropped retries, lost queued exports and misplaced metrics.
We shipped v6.0.0b8 this week. It adds support for OpenTelemetry 1.45, a compression option with experimental zstd support for large spans, console attributes that can be shown without verbose output, and FastAPI instrumentation that no longer creates duplicate telemetry. Alongside the release, several fixes should make exported data more reliable: raw-byte OTLP posts now go through the retry path, the disk retryer no longer deletes queued exports after permanent errors such as a 401, metrics respect an explicitly passed context, update name keeps the span message in sync, integers below the int64 minimum are converted rather than dropped, and fields with repr set to false are no longer exported. The command line interface also now falls back to the environment base URL setting.
Week of September 28, 2026
What shipped
- Query limits are now documented in a reference page showing limits by organization plan across web UI, read tokens, MCP, and the public API. Pull request #2498
- OpenTelemetry eBPF Instrumentation guide added with setup instructions for Docker Compose and Kubernetes, including OTLP/HTTP export, endpoint configuration, and verification steps. Pull request #2414
- AI Gateway guides published covering setup, provider configuration, routing, protections, optimizations, and spending controls. Pull request #2492
- Documentation clarified the distinction between human annotations from reviewers and end-user feedback scores from live evaluation. Pull request #2504
- TypeScript documentation navigation now mounted directly from the logfire-js repository instead of duplicated in Logfire docs. Pull request #2496
- Documentation updated explaining how cases are ingested into hosted datasets, correcting outdated concepts from earlier docs restructuring. Pull request #2268
- Gateway guides now link directly to corresponding Logfire setup pages for Connect, Providers, Endpoints, Guardrails, and related features. Pull request #2495
- Pyodide dependencies for OpenTelemetry API, instrumentation, and semantic conventions aligned with existing SDK and exporter bounds. Pull request #2493
Why it matters
This week brings documentation improvements that help users understand query limits, set up complex instrumentation scenarios like eBPF and AI Gateway, and navigate between related products. Updates also clarify evaluation concepts and clean up outdated documentation from earlier restructuring.
Changelog entry
- Added query limits reference page documenting limits by organization plan for web UI, read tokens, MCP, and public API Pull request #2498
- Added OpenTelemetry eBPF Instrumentation guide with Docker Compose and Kubernetes setup, OTLP/HTTP export, and verification steps Pull request #2414
- Added AI Gateway guides for setup, provider configuration, routing, protections, optimizations, and spending controls Pull request #2492
- Clarified documentation distinguishing human annotations from trusted reviewers against rubrics from end-user feedback scores Pull request #2504
- TypeScript documentation navigation now included from logfire-js repository with unified page ordering and aliases Pull request #2496
- Updated documentation on how cases are ingested into hosted datasets with corrected product information Pull request #2268
- Added direct links from Gateway guides to Logfire Connect, Providers, Endpoints, Guardrails, and related pages Pull request #2495
- Aligned Pyodide OpenTelemetry dependencies for core API, instrumentation, and semantic conventions with SDK and exporter bounds Pull request #2493
New this week: query limits documented by plan, OpenTelemetry eBPF setup guides, AI Gateway controls walkthrough, and TypeScript docs mounted from logfire-js.
Logfire docs expanded this week with query limit references, comprehensive OpenTelemetry eBPF Instrumentation guides for Docker and Kubernetes, task-focused AI Gateway setup covering providers, routing, protections, and spending controls. TypeScript documentation is now maintained directly in logfire-js and mounted in the main docs.
Week of September 21, 2026
What shipped
- V6.0.0b7 released with a fix to configure proxy managers before other threads can use them. Release
- V5.1.1 released with fixes for project setup on accounts without organizations and TCP keepalive improvements. Release
- V6.0.0b6 released making the logfire package own the logfire command and requiring logfire-cli 0.1.8 or later. Release
- TCP keepalive and idle connection recycling enabled in Logfire's HTTP sessions to prevent stalls from silently dropped connections. Pull request #2309
- V6.0.0b4 released with instrument_mcp() support for mcp 2 and fastmcp 4, and added logfire.instrument_monty(). Release
- Documentation updated to clarify that custom Gateway provider endpoints require a paid plan. Pull request #2484
- Dashboards guide rewritten with updated screenshots reflecting new design and changed features. Pull request #2460
- Coverage reporting moved from Codecov to python-coverage-comment-action matching Pydantic's setup. Pull request #2485
Why it matters
Three beta releases landed in the v6.0.0 line with fixes for proxy configuration and MCP instrumentation, while v5.1.1 brings connection stability improvements to the maintenance branch. Documentation updates clarify plan requirements and reflect current UI behavior.
Changelog entry
- Configure proxy managers before other threads can use them to avoid race conditions Release
- Handle project setup for accounts without organizations Release
- Enable TCP keepalive and recycle idle connections in HTTP sessions Release
- Make logfire package own logfire command and require logfire-cli 0.1.8 or later Release
- Add instrument_mcp() support for mcp 2 and fastmcp 4 Release
- Add logfire.instrument_monty() Release
Logfire v6.0.0b7, v6.0.0b6, and v5.1.1 released. Beta updates fix proxy manager race conditions and clarify command ownership. v5.1.1 improves HTTP connection stability with TCP keepalive and idle recycling.
This week saw three releases across the Logfire lines. v6.0.0b7 and v6.0.0b6 beta releases addressed proxy configuration race conditions and clarified the logfire command ownership with logfire-cli. v5.1.1 on the maintenance branch brings TCP keepalive and connection recycling to prevent stalls from silently dropped connections. Documentation updates clarify custom Gateway provider plan requirements and reflect current UI behavior in dashboards and service levels guides.
Week of September 14, 2026
What shipped
- Logfire 6 split into separate logfire-sdk and logfire-cli packages with the logfire package installing both for backward compatibility. Pull request #2409
- Released Logfire 6.0.0b1 with the SDK and CLI separation, preserving existing imports and optional extras. Release
- Released Logfire 6.0.0b3 requiring logfire-cli 0.1.5 or later. Release
- Added logfire.instrument_snowflake() to instrument Snowflake connector queries with span per query including SQL text, query ID, row count, and connection identity. Pull request #2348
- Fixed logfire.instrument_mcp() to work with MCP 2 and fastmcp 4 by updating module imports. Pull request #2439
- Logfire run now supports executing installed Python
console_scriptsentry points like pytest and uvicorn in instrumented processes. Pull request #2427 - Updated public quickstart documentation to use uvx logfire-cli setup as the primary command. Pull request #2435
- Added documentation for passwordless email-code sign-in and two-factor behavior. Pull request #2440
- Documented public conversation sharing in Early Access including security boundaries and span exposure options. Pull request #2445
- Embedded tutorial videos for Services, Session Replays, and Frontend guides using Cloudflare Stream. Pull request #2436
Why it matters
Logfire 6.0.0 is now in beta with the architecture split into separate SDK and CLI packages, new database instrumentation for Snowflake, MCP compatibility fixes, and expanded documentation covering email authentication, public sharing, and setup workflows. This week consolidates the beta releases and addresses core integration compatibility while improving getting-started guidance.
Changelog entry
- Split logfire into logfire-sdk and logfire-cli with logfire package installing both Pull request #2409
- Released v6.0.0b3 with logfire-cli 0.1.5 requirement Release
- Released v6.0.0b2 with logfire-cli 0.1.4 requirement and console scripts support Release
- Added instrument_snowflake() for Snowflake connector instrumentation Pull request #2348
- Fixed instrument_mcp() compatibility with MCP 2 and fastmcp 4 Pull request #2439
- Logfire run now executes installed Python
console_scriptsentry points Pull request #2427 - Updated browser instrumentation to use configureFrontend for React and Next.js Pull request #2425
- Updated quickstart to use uvx logfire-cli setup as primary command Pull request #2435
- Added documentation for email-code sign-in and two-factor authentication Pull request #2440
- Documented public conversation sharing and security boundaries Pull request #2445
- Reorganized administration documentation with task-oriented management groups Pull request #2431
- Clarified Personal plan billing excludes overage charges unlike paid plans Pull request #2420
Logfire 6.0.0b3 is out. The new split architecture makes logfire-cli independent, Snowflake instrumentation is here, and logfire run now handles console scripts. Try the uvx setup command in the updated docs.
Logfire 6 beta continues to evolve. This week brings the third beta release with logfire-cli 0.1.5, new Snowflake query instrumentation, MCP protocol compatibility fixes, and enhanced setup documentation featuring email sign-in and passwordless authentication. The architecture now cleanly separates the Python SDK from the CLI while maintaining full backward compatibility.