Bedrock WordPress Plugin Update

### 1. Update Plugins via Composer
Since Bedrock manages dependencies with Composer, you should update plugins by adjusting the `composer.json` file and running the Composer update command.

– Open the `composer.json` file in the Bedrock root directory.
– Find the plugin under `"require"` and specify the desired version. For example:

"require": {
    "wpackagist-plugin/your-plugin": "^1.5"
  }

– To update to the latest version compatible with your version constraint, run:

composer update wpackagist-plugin/your-plugin

### 2. Clear the Cache (if necessary)
If you have any caching enabled, clear it after updating plugins to ensure no cached versions interfere with the updated plugin files.

### 3. Test Updates
Once the update is complete, test your WordPress site locally (and in staging, if possible) to confirm that the updates didn’t cause any issues, especially with Sage theme customizations.

### Notes
– Bedrock uses `wpackagist` to pull in plugins as Composer dependencies. Make sure you are referencing the plugins correctly with `wpackagist-plugin/` prefix.
– In Sage, you might also need to recompile assets if any frontend changes were required for compatibility.

composer update wpackagist-plugin/your-plugin

tells Composer to:

1. **Update the Specified Plugin**: Composer will look at the version constraints defined in your `composer.json` file for `wpackagist-plugin/your-plugin` and attempt to update it to the latest version that fits within those constraints.

2. **Download and Replace Plugin Files**: Composer will download the newer version of the plugin and replace the existing plugin files in the `vendor` directory.

3. **Update the Composer Lock File**: If an update is performed, `composer.lock` will be updated to reflect the new version and dependencies of the plugin. This file is essential for ensuring consistency across environments.

4. **Check for Dependency Compatibility**: Composer will also check other dependencies in your `composer.json` to ensure the update doesn’t introduce conflicts. If other plugins or packages rely on a specific version, it will notify you of any conflicts that need resolving.

After running this command, your plugin should be updated to the latest compatible version.

If you want to **update the version constraint** in `composer.json` for the plugin, here are a couple of ways to do it:

### Option 1: Manually Update `composer.json`
1. Open `composer.json` in a text editor.
2. Locate the plugin under the `"require"` section, and change its version constraint to the desired one, for example:

"require": {
       "wpackagist-plugin/your-plugin": "^2.0"
   }

3. Run:

composer update wpackagist-plugin/your-plugin

This will install the version matching the new constraint and update `composer.lock` accordingly.

### Option 2: Use `composer require` to Update Constraint
You can also use the `composer require` command to update the version constraint directly from the terminal:

composer require wpackagist-plugin/your-plugin:^2.0

This command:
– Updates the version constraint in `composer.json`.
– Installs the new version and updates `composer.lock`.