Skip to content

Releases: lunetics/LuneticsLlmCostTrackingBundle

v0.3.0

26 Feb 00:08

Choose a tag to compare

What's Changed

Other Changes

  • feat: replace default_models.php with auto-generated snapshot fallback by @lunetics in #9

Full Changelog: v0.2.1...v0.3.0

v0.2.1

25 Feb 18:38

Choose a tag to compare

Full Changelog: v0.2.0...v0.2.1

v0.2.0

25 Feb 18:24

Choose a tag to compare

What's Changed

Other Changes

  • feat: add Monolog cost logging via configurable channel by @lunetics in #8

Full Changelog: v0.1.4...v0.2.0

v0.1.4

25 Feb 12:22

Choose a tag to compare

Full Changelog: v0.1.3...v0.1.4

v0.1.3

25 Feb 12:07
d48cb31

Choose a tag to compare

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-bundle and symfony/ai-platform constraints from ^0.4|^1.0 to >=0.4.0 <2.0.0

v0.1.1 (included in changelog)

  • Fixed cache:clear crash in Symfony dev mode caused by PHP objects being passed as DI constructor arguments

v0.1.2

25 Feb 12:02

Choose a tag to compare

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.x0.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

25 Feb 11:59
c4066dd

Choose a tag to compare

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.

v0.1.0

25 Feb 11:13

Choose a tag to compare

What's Changed

Other Changes

  • Fix CI: allow symfony/flex Composer plugin by @lunetics in #1
  • models-pricing: dynamic pricing, code review fixes, test coverage by @lunetics in #2
  • Extract CostTracker service for userland consumption by @lunetics in #3
  • Add release workflow and Makefile targets by @lunetics in #4
  • chore: production readiness improvements by @lunetics in #5

New Contributors

Full Changelog: https://github.com/lunetics/LuneticsLlmCostTrackingBundle/commits/v0.1.0