Release Notes

What's new in the latest version of auditor.

The format is inspired by Keep a Changelog, and this project adheres to Semantic Versioning.

---

Version 2.x

auditor v2.0.0

BC changes

• Providing an integer value for the keep argument of the audit:clean command is no longer supported. Use the ISO 8601 duration format (e.g. P12M) instead.
• Passing name and value to the Query::addFilter() method is no longer supported. Pass it a FilterInterface object instead.
• Query::addRangeFilter() method has been removed, you should call Query::addFilter() instead and pass it a RangeFilter object.
• Query::addDateRangeFilter() method has been removed, you should call Query::addFilter() instead and pass it a DateRangeFilter object.

Changes

• Drop PHP 7.2 and 7.3 support.
• Drop Symfony 3.4 support.
• Audit relationship refs (#60)

---

Version 1.x

auditor v1.3.1

Changes

• Blocks installation along with doctrine/dbal 3.x

---

auditor v1.3.0

Fixes

• #35 - Fixes storage mapper callable handling
• #41 - Remove flusher callback from logger on rollback
• #46 - Resets transaction once processed by the onFlush event subscriber
• #50 - Fix an edge case where annotations where not loaded if audited entities were set in configuration

Changes

• #40 - Add support to php 8 attributes
• #31 - Add audit event's database ID on LifecycleEvent payload in DoctrineProvider
• Properly handle (unsupported) composite primary keys: throw a dedicated exception when such an entity is audited.

---

auditor v1.2.0

Fixes

• #11 - Is auditor using the database during a cache:clear?
• #29 - reader->createQuery->addFilter by array of object_ids
• #243 (auditor-bundle) - How to store audit tables in other database ?
• #244 (auditor-bundle) - AuditReader->getAudits by array of ids
• #245 (auditor-bundle) - Doctrine Migrations not managing audit table
• #249 (auditor-bundle) - Doctrine migrations wants to drop tables

Changes

• #26 - Fixed multiple entity manager setups
• #30 - Annotations lazy loading
• #28 - Enhanced query filters

Query::addFilter(string $name, $value)
Query::addRangeFilter(string $name, $minValue, $maxValue)
Query::addDateRangeFilter(string $name, $minValue, $maxValue)

are now deprecated in favor of

Query::addFilter(FilterInterface $filter)

There are several kinds of filters:

• SimpleFilter lets you filter by a specific value or set of values
• RangeFilter lets you filter by a range of values
• DateRangeFilter lets you filter by a range of dates

More details in the documentation

---

auditor v1.1.0

Changes

• #19 - Better handling of binary data
• #20 - UID support (Ramsey UUID/Symfony ULID)
• #21 - Fixed a Query bug using multiple filters
• #24 - Fixed a bug related to storage entity managers

---

auditor v1.0.1

Changes

• Updated CI to ensure proper Symfony versions are installed during tests (3.4, 4.4 and 5.x are tested)
• Fixed a failing test with Symfony 3.4

---

auditor v1.0.0

Initial release.

The purpose of auditor is to provide an easy and standardized way to collect audit logs.

This library is architected around two concepts:

• Auditing services responsible for collecting audit events
• Storage services responsible for persisting audit traces

Those two kind of services are offered by Providers and a default one is included with this library: DoctrineProvider

DoctrineProvider offers both auditing services and storage services and creates audit logs for all Doctrine ORM database related changes.

---