What pydantic/logfire shipped
Written by FoxPlug from public releases; not affiliated with Pydantic. An automatic summary of the public release, pull request and commit data of github.com/pydantic/logfire. Pydantic did not write it and does not use or endorse FoxPlug. Every line links to the public change it describes.
Get a weekly update like this for your product, free
Week of September 21, 2026
What shipped
- v6.0.0b7 released with a fix to configure proxy managers before other threads can use them [3]. Release
- v5.1.1 released with fixes for project setup on accounts without organizations and TCP keepalive improvements [2]. Release
- v6.0.0b6 released making the logfire package own the logfire command and requiring logfire-cli 0.1.8 or later [8]. Release
- TCP keepalive and idle connection recycling enabled in Logfire's HTTP sessions to prevent stalls from silently dropped connections [19]. Pull request #2309
- v6.0.0b4 released with instrument_mcp() support for mcp 2 and fastmcp 4, and added logfire.instrument_monty() [27]. Release
- Documentation updated to clarify that custom Gateway provider endpoints require a paid plan [1]. Pull request #2484
- Dashboards guide rewritten with updated screenshots reflecting new design and changed features [13]. Pull request #2460
- Coverage reporting moved from Codecov to python-coverage-comment-action matching Pydantic's setup [0]. 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 [3] Release
- Handle project setup for accounts without organizations [2] Release
- Enable TCP keepalive and recycle idle connections in HTTP sessions [2] Release
- Make logfire package own logfire command and require logfire-cli 0.1.8 or later [8] Release
- Add instrument_mcp() support for mcp 2 and fastmcp 4 [27] Release
- Add logfire.instrument_monty() [27] 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
- Event [15]: Logfire 6 splits into logfire-sdk and logfire-cli as separate distributions, with logfire installing both while maintaining backward compatibility. Release
- Event [5]: Logfire 6.0.0b3 released, requiring logfire-cli 0.1.5 or later. Release
- Event [8]: Logfire 6.0.0b2 released with support for console scripts in logfire run. Release
- Event [4]: instrument_mcp() now works with mcp 2 and fastmcp 4. Pull request #2439
- Event [20]: Added instrument_snowflake() to instrument snowflake-connector-python with span per query including SQL text and row count. Pull request #2348
- Event [12]: logfire run now executes installed Python
console_scriptsentry points cross-platform. Pull request #2427 - Event [1]: Public quickstart documentation updated to use uvx logfire-cli setup as the primary setup command. Pull request #2435
- Event [0]: Added public guide for Public Conversations in Early Access covering security boundaries, expiration, and management. Pull request #2445
- Event [3]: Documented passwordless account creation and email-code sign-in with two-factor behavior. Pull request #2440
- Event [7]: Embedded tutorial videos for Services, Session Replay investigation, and Frontend guides. Pull request #2436
Why it matters
Logfire 6 is now separated into independent SDK and CLI packages, providing better modularity for users who need only the Python SDK. Multiple new integrations and features landed this week, including Snowflake support and MCP 2 compatibility. Documentation improvements make onboarding simpler with the CLI-first setup path.
Changelog entry
- Breaking: Logfire 6 splits into logfire-sdk and logfire-cli packages; logfire installs both by default Release
- Released v6.0.0b3 with logfire-cli 0.1.5 requirement Release
- Released v6.0.0b2 with console scripts support in logfire run Release
- Added instrument_snowflake() for snowflake-connector-python instrumentation Pull request #2348
- Fixed instrument_mcp() compatibility with mcp 2 and fastmcp 4 Pull request #2439
- logfire run now supports executing
console_scriptsentry points Pull request #2427 - Updated browser instrumentation to use configureFrontend for React and Next.js Pull request #2425
- Documented email-code sign-in and passwordless account creation Pull request #2440
Logfire 6.0.0b3 shipped. SDK and CLI now split into separate packages—install logfire-sdk alone if you don't need the CLI. New Snowflake integration and console script support in logfire run.
Logfire 6.0.0b3 is out. We've separated the SDK and CLI into distinct packages for better modularity—install logfire-sdk independently if the CLI isn't needed. This week also brought instrument_snowflake() for Snowflake connector instrumentation, fastmcp 4 support, and console script execution in logfire run. Documentation improvements streamline setup with CLI-first guidance.