Upgrading

Versioning

quiet-guard/monitor-symfony-bundle follows semantic versioning. Patch and minor releases are backward compatible; breaking changes are reserved for major versions and called out here.

The bundle depends on the framework-agnostic core quiet-guard/monitor-php, which is upgraded in lock-step. Composer resolves both together.

Compatibility

The Symfony components the bundle requires, symfony/config, symfony/dependency-injection, symfony/event-dispatcher and symfony/http-kernel, are constrained to ^6.4|^7.0|^8.0.

The ingestion API the bundle talks to (/api/v1/...) is platform-neutral and versioned independently of the package, so a recent bundle keeps working against a running server of the same major API version.

How to upgrade

composer update quiet-guard/monitor-symfony-bundle

Because configuration is declarative and environment-driven, most upgrades require no code changes, new options arrive with safe defaults and are opt-in.

Things to verify after an upgrade

• Config tree: compare your config/packages/monitor.yaml against the current Configuration reference and merge any new keys.
• Environments: confirm environments still matches where you want reporting active (an empty list means all environments, including dev).
• Log handler: if you forward logs, check that the monitor handler is still attached to Monolog and that monolog/monolog ^3.0 is installed.
• Scrub list: setting scrub replaces the defaults, so re-check that your list still includes every key you want masked.

Removing the bundle

composer remove quiet-guard/monitor-symfony-bundle

Then remove the bundle entry from config/bundles.php (if you registered it by hand), delete config/packages/monitor.yaml, drop any monitor handler from your Monolog config, and remove the MONITOR_* variables from your .env.