You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe your use case and the problem you are facing
For wp core verify-checksums the --version option is available to specify WP core version.
This is very useful in a deploy (update) process to check if the codebase is on the expected version.
If verify returns success, then skip download and/or report no change, if verification fails then download the right (usually newer) version. So it's possible to create an idempotent process.
It would be great to apply this logic to plugins also!
Describe the solution you'd like
Adding a --version option to plugin verify-checksums where we could directly set the version not just getting that from the plugin.
Of course, this would make sense only if a single plugin is provided, but this can be handled by ignoring --version if --all or multiple plugins are passed in.
Note: I'm happy to submit a PR.
The text was updated successfully, but these errors were encountered:
I was just wondering about the chances of installing (or verify) two different plugins that happens to have the same version. With --all, I believe, that chance gets close to zero... :)
But why not indeed? There can be a use-case, so don't limit ourselves.
Feature Request
Describe your use case and the problem you are facing
For
wp core verify-checksums
the--version
option is available to specify WP core version.This is very useful in a deploy (update) process to check if the codebase is on the expected version.
If verify returns success, then skip download and/or report no change, if verification fails then download the right (usually newer) version. So it's possible to create an idempotent process.
It would be great to apply this logic to plugins also!
Describe the solution you'd like
Adding a
--version
option toplugin verify-checksums
where we could directly set the version not just getting that from the plugin.Of course, this would make sense only if a single plugin is provided, but this can be handled by ignoring
--version
if--all
or multiple plugins are passed in.Note: I'm happy to submit a PR.
The text was updated successfully, but these errors were encountered: