Versions 3.16.1 and 3.16.2 were committed directly to the WordPress.org SVN repository due to the build workflow from GitHub being broken. I need to tag and publish releases for these on GitHub.
I think I can follow the usual tag and release process and allow the deployment workflow to fail when it attempts to tag the release(s) on WordPress.org that already exist, but I want to verify that first. I may disable the deployment workflow while I publish these two releases.
This will publish the releases to Packagist.org too.
Once that's done then we're back to business as usual.
Versions 3.16.1 and 3.16.2 were committed directly to the WordPress.org SVN repository due to the build workflow from GitHub being broken. I need to tag and publish releases for these on GitHub.
I think I can follow the usual tag and release process and allow the deployment workflow to fail when it attempts to tag the release(s) on WordPress.org that already exist, but I want to verify that first. I may disable the deployment workflow while I publish these two releases.
This will publish the releases to Packagist.org too.
Once that's done then we're back to business as usual.
Related support forum thread: https://wordpress.org/support/topic/latest-version-on-packgist/