Upgrading

Versioning

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

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

Compatibility

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

How to upgrade

composer update quiet-guard/laravel-monitor

After upgrading, re-check your config against the current defaults. If you published config/monitor.php, compare it with the package's shipped file and merge any new keys:

# Inspect the latest published defaults
php artisan vendor:publish --tag=monitor-config

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

Things to verify after an upgrade

• Environments: confirm MONITOR_ENVIRONMENTS still matches where you want reporting active (default production,staging). See Configuration.
• Queue: if you forward via a queue (MONITOR_QUEUE), make sure a worker is running so SendExceptionToMonitor / SendLogsToMonitor jobs are processed.
• Scrub list: if you published the config, re-check that your custom scrub entries are still present and complete.
• Backups: verify the relevant dump binary (mysqldump / pg_dump) is available on the host if you rely on encrypted backups.

Removing the SDK

composer remove quiet-guard/laravel-monitor

Auto-discovery means there is nothing else to unregister. If you published the config, delete config/monitor.php and drop the MONITOR_* variables from your .env.