Repository navigation
Releases: lunetics/LuneticsLlmCostTrackingBundle
Release list
v0.6.0
What's Changed
Other Changes
- feat: surface skipped calls in the profiler panel (breaking: CostTrackerInterface) by @lunetics in #12
Full Changelog: v0.5.0...v0.6.0
v0.5.0
v0.4.0
v0.3.0
v0.2.1
v0.2.0
v0.1.4
v0.1.3
Documentation
Backfills the CHANGELOG with entries for v0.1.1 and v0.1.2, which were released without changelog updates. Also adds the version comparison link footer so each entry links to its GitHub diff.
v0.1.2 (included in changelog)
- Widened
symfony/ai-bundleandsymfony/ai-platformconstraints from^0.4|^1.0to>=0.4.0 <2.0.0
v0.1.1 (included in changelog)
- Fixed
cache:clearcrash in Symfony dev mode caused by PHP objects being passed as DI constructor arguments
v0.1.2
Bug Fix
Widened symfony/ai-bundle and symfony/ai-platform version constraints
Problem: The previous constraint ^0.4|^1.0 had a gap. In Composer, ^0.4 means >=0.4.0 <0.5.0 (the caret locks the leftmost non-zero digit — for 0.4 that is the minor, not the major). Any symfony/ai release in the 0.5.x–0.9.x range would not satisfy the constraint, causing installation to fail.
Fix: Changed to >=0.4.0 <2.0.0, which matches all 0.4+ and 1.x releases.
Upgrade: No configuration changes required. Update your composer.json constraint to ^0.1.2 or ~0.1.2.
v0.1.1
Bug Fix
Fix cache:clear crash in Symfony dev environment
Problem: Installing this bundle and running bin/console cache:clear with kernel.debug=true (dev mode) threw:
Unable to dump a service container if a parameter is an object or a resource,
got Lunetics\LlmCostTrackingBundle\Model\ModelDefinition
Symfony's ContainerBuilderDebugDumpPass serialises the compiled container to XML during dev builds. It cannot serialise plain PHP object instances as service constructor arguments.
Fix: ModelDefinition and CostThresholds arguments in loadExtension() are now described as inline Definition objects (DI metadata) rather than instantiated PHP objects. Named setArgument('$param', value) calls are used for clarity and resilience to constructor reordering.
Upgrade: No configuration changes required. Update your composer.json constraint to ^0.1.1 or ~0.1.1.