Upgrading

The plugin follows the same build-and-deploy flow as the initial installation: because the framework-agnostic core is vendored at build time, an upgrade means shipping a freshly built copy of the plugin folder.

Versioning

The plugin version is declared in the header of laravel-monitor.php (currently 0.2.0). It tracks the version of the bundled core quiet-guard/monitor-php, which is required as ^0.2. While both are pre-1.0, treat minor releases as potentially containing breaking changes and read the release notes before upgrading.

Upgrade steps

1. Obtain the new plugin source and run composer install --no-dev inside the laravel-monitor/ folder to vendor the current core.
2. Zip the rebuilt laravel-monitor folder (including its vendor/ directory).
3. In wp-admin, deactivate the existing Quiet Guard plugin, then upload the new zip via Plugins → Add New → Upload Plugin (WordPress will offer to replace the current copy). Alternatively, replace the folder under wp-content/plugins/ over SSH.
4. Activate the plugin.

Your settings are stored in the WordPress option laravel_monitor_options and are not removed by deactivating or replacing the plugin, so the server URL, project key, environments and release survive an upgrade. After upgrading, open Settings → Quiet Guard to confirm the values are intact.

After upgrading

Trigger a test error and confirm it still reaches your dashboard, as described in Usage. If capture stops, the most common cause is a missing vendor/ directory, the rebuilt folder must include it, otherwise the plugin activates but captures nothing; an error notice in wp-admin now flags this state and asks you to run composer install.

On the roadmap

Future versions are expected to add environment-aware filtering for WordPress and dependency/vulnerability scanning for WordPress core, plugins and themes (served from a WordPress-specific advisory source, distinct from the Packagist source used for Composer-based apps). Encrypted storage of captured content is enforced server-side, per team, independently of the plugin version.