WORDPRESS PLUGIN
Let WordPress handle your plugin updates.
Make every installed plugin eligible for unattended updates. Plugins listed in Devenia’s signed channel receive its checked packages; other plugins keep their own update providers.
Automatic updates apply to every plugin
Activating this updater enables automatic updates for all installed plugins, including future installs. Its policy applies even when a plugin is absent from WordPress’s saved per-plugin opt-in list. There is no settings screen for choosing exceptions.
Listed in Devenia’s channel
Listed plugins receive packages from downloads.devenia.com through the normal WordPress update interface. The signed list decides which plugin files belong to this channel; it can include a designated upstream plugin as well as Devenia plugins.
Other installed plugins
For example, a contact-form or shop plugin outside the signed list continues to use its own registered update provider. It also becomes eligible for automatic updates. This updater does not replace that provider’s package checks with Devenia’s checks.
The package must match the signed reference
Publisher: the update list needs a valid Devenia digital signature before its entries can be accepted. The signature identifies authorised update information.
Address: a listed package must use the exact address tied to that release on downloads.devenia.com. Another ZIP on the same domain is not an interchangeable package.
File: a recognised package download must match the published SHA-256 hash — a fingerprint of the file’s bytes. A mismatch stops that download from being installed.
The matching package follows the installation track; the different one stays outside. The illustration explains file identity, not a guarantee that an update will suit every site.
Eligible does not mean updated
WordPress still needs to run its scheduled update jobs and write the plugin files. Hosting restrictions and other update hooks can affect the result. Keep a restorable backup and check the site after an update.
1. Check the requirements
You need WordPress 6.8 or later, PHP 7.4 or later with Sodium support, and server access to downloads.devenia.com. Sodium verifies the signature. Confirm that WordPress can run scheduled tasks and write to the plugin directory.
2. Install and check for updates
In WordPress, open Plugins → Add New Plugin → Upload Plugin. Choose the downloaded ZIP, install it and activate Devenia MCP Updater. Then open Dashboard → Updates and check for updates. You do not need an external Git-hosting account.
3. Confirm the result
After an update runs, check the installed version and activation state. Test the function that matters on your site: for example, submitting a form or adding an item to the basket. An available update notice is not proof of a completed installation.
If nothing updates
Check Tools → Site Health for scheduled-task problems and ask your host about update or filesystem restrictions. See WordPress’s automatic-update guide for its scheduling and troubleshooting advice.
For MCP users
WordPress updates work without an MCP client. When using the MCP plugin-upload interface, the updater permits URL installation only for an exact eligible package in the signed list. It does not turn arbitrary ZIP URLs into approved uploads.
Know what the checks prove
The checks establish the signed update information and the recognised package’s identity. They do not replace compatibility testing or backups. This plugin changes plugin-update eligibility; it does not set the update policy for themes or WordPress core.
Make plugin updates part of the routine
Install the updater when you want automatic updates across your plugins. Check the requirements first, then verify an installed update on the site you rely on.