diff --git a/README.md b/README.md index 06c6fe7..6a0375f 100644 --- a/README.md +++ b/README.md @@ -51,7 +51,7 @@ The `wp maintenance` commands don't need the full environment: any `wp` executab To find out which packages have unreleased changes, run `wp maintenance release plan --bundle`. It makes no changes, and for each package it says whether a milestone is ready for `wp maintenance release generate` or what a maintainer still needs to decide, such as which milestone a merged pull request belongs to. -To check the locked dependencies of the bundle for security advisories, run `wp maintenance dependencies audit`. It runs `composer audit` against the composer.lock as committed, so it reports what the Code Quality workflow fails on, and marks the packages that are only needed for development, as they don't ship in the Phar. +To check the locked dependencies of the bundle for security advisories, run `wp maintenance dependencies audit`. It runs `composer audit` against the composer.lock as committed, so it reports what the Code Quality workflow fails on, and marks the packages that are only needed for development, as they don't ship in the Phar. `wp maintenance dependencies update` then updates the affected packages within the constraints of composer.json and opens a pull request with the new composer.lock. Pass `--dry-run` to see the changes first. ## Using