Skip to content

v0.38.0

Compare
Choose a tag to compare
@alexmojaki alexmojaki released this 31 May 13:20
· 586 commits to main since this release
d27759f

What's Changed

BREAKING CHANGE: Calling logfire.info, logfire.error, logfire.span etc. will no longer automatically configure logfire if it hasn't been configured already. Instead it will emit a warning and not log anything.
Users must call logfire.configure() before they want logging to actually start, even if they don't pass any arguments to configure and all configuration is done by environment variables.
Using integrations like logfire.instrument_fastapi() before calling configure will also emit a warning but it will still set up the instrumentation, although it will not log anything until configure is called.

Full Changelog: v0.37.0...v0.38.0