This release adds 1 notable feature for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+3 more
Affected surfaces
Summary
AI summaryFixes template access for JSON fields with hyphens by introducing a json variable and updating the migration script.
Full changelog
This release mainly fixes a problem regarding accessing certain JSON fields from a log entry via templates. Template fields that access top-level JSON keys and contain hyphens don't work, since expressions like {{ some-key }} are not valid Python identifiers.
As a workaround, you have to use the new json field, which exposes the full JSON object, and access these keys using bracket notation instead:
{{ json["some-key"] }}
If you haven't yet migrated from v1.8 to v2 you can use the migration script and it will handle these edge cases for you.
Additionally to the v2 docs can now also check out the v1.8 docs as the documentation site now has a version switcher.
What's Changed
- fix: expose JSON fields from log via template variable to support hyphenated keys in templates
- refactor: change default ntfy icon url from github to selfh.st
- feat(migration): update migration script to migrate hyphenated template variables to json['key'] notation
- chore(deps): bump requests from 2.33.1 to 2.34.0 by @dependabot[bot] in https://github.com/clemcer/LoggiFly/pull/96
- chore(deps): bump pydantic from 2.13.3 to 2.13.4 by @dependabot[bot] in https://github.com/clemcer/LoggiFly/pull/95
- docs: add versioned documentation in https://github.com/clemcer/LoggiFly/pull/98
Full Changelog: https://github.com/clemcer/LoggiFly/compare/v2.0.0...v2.0.1
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
Related context
Related tools
Beta — feedback welcome: [email protected]