Timestampable Bundle Laravel Package

What's Changed

• remove $ so gitclip works by @tacman in https://github.com/andanteproject/timestampable-bundle/pull/10
• update phpstan to 2.0 and fix errors it reports by @tacman in https://github.com/andanteproject/timestampable-bundle/pull/11
• [codex] Fix Symfony extension deprecation by @tacman in https://github.com/andanteproject/timestampable-bundle/pull/13

New Contributors

• @tacman made their first contribution in https://github.com/andanteproject/timestampable-bundle/pull/10

Full Changelog: https://github.com/andanteproject/timestampable-bundle/compare/3.1.0...3.1.1

This release adds Symfony 8 support, an optional metadata cache warmer, and a refactored internal metadata structure for timestampable entities. Existing applications using interfaces and configuration remain fully supported; no breaking changes.

Added

• Symfony 8 support
  The bundle is compatible with Symfony ^5.0 | ^6.0 | ^7.0 | ^8.0 and Symfony Clock ^6.2 | ^7.0 | ^8.0. CI runs against Symfony 8.0 and Doctrine ORM 3.5 for Symfony 8 compatibility.

• Optional metadata cache warmer
  Timestampable metadata can be warmed at container build time so the first request does not build it on the fly.

  • New config option: andante_timestampable.metadata_cache_warmer_enabled (default: false). Set to true to enable the warmer. It's suggested to use it in prod environments.

Upgrade

1. Update the bundle to this version.

2. (Optional) Enable metadata cache warmer for prod environments:

   andante_timestampable:
     metadata_cache_warmer_enabled: true
   

Built with ❤️ by the Andante Project team.

Symfony Clock 7

Support Symfony 7

Library does not override your createdAt and updatedAt values when you set them explicitly

• Move min version of PHP to 8.1;
• Solve Symfony/doctrine-bridge 6.3 deprecation;
• Use clock component instead of new \DateTimeImmutable.

• Adding support to Event Manager 2.0
• Correcting deprecations in the event and tests.
• Updating the annotation tests to attributes

Thanks to @danielesteve-cibervoluntarios!

Fix support for Doctrine Bundle 2.3