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:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18

name: Plugin asset/readme update
on:
  push:
    branches:
    - master
jobs:
  trunk:
    name: Push to trunk
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@master
    - name: WordPress.org plugin asset/readme update
      uses: 10up/action-wordpress-plugin-asset-update@stable
      env:
        SVN_PASSWORD: ${{ secrets.SVN_PASSWORD }}
        SVN_USERNAME: ${{ secrets.SVN_USERNAME }}
        SLUG: login-devices
        IGNORE_OTHER_FILES: true

Some things that you might want to pay attention to are:

  1. The branch that this action should check on, could be your main or trunk.
  2. The SLUG in case the slug in WordPress repository is different from GitHub.
  3. IGNORE_OTHER_FILES is set to true for 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.txt and WordPress asset directory updates.