If you publish plugins to the official WordPress.org repository, you normally will get an email reminder to update your plugin prior to the major WordPress release. As a plugin developer, it is your responsibility to make sure the plugin you developed is compatible with the latest WordPress release.
To mark your plugin as compatible, all you have to do is update the
Tested up to: value in the
readme.txt to the latest WordPress version.
It can be quite tedious if you have lots of plugins plus it is using SVN (if I can avoid this, I definitely will), so I automate the updates with SVN using 10up/action-wordpress-plugin-asset-update.
The workflow file is fairly straightforward, this is what I put in one of my plugins:
Some things that you might want to pay attention to are:
- The branch that this action should check on, could be your
SLUGin case the slug in WordPress repository is different from GitHub.
IGNORE_OTHER_FILESis set to
truefor me, because there are Composer-related files that are preventing the script from running because it tries to check the differences to make sure it only runs on
readme.txtand WordPress asset directory updates.