Release automation

[gabrielcld2]

Deployment process

This is what the production release process will look like from now on:

1. Prepare master branch

This is pretty much as before:

• prepare all changes in a PR against master
• this should also include the following:
  • updated version in both .version and package.json
  • updated readme.txt changelog
• merge the master PR

2 Create and publish GH release

This is also similar to what was done before:

• Go to the repository on GitHub → Releases → Draft a new release
  • Create a new tag (e.g. 3.3.4) targeting master
  • Set the release title and notes (copy and format the changelog from the readme.txt)
  • Publish as a standard release
  • Note: pre-release can be used to do a dry-run instead which will trigger the workflow but won't push to wp.org's SVN repository.

3. The GH workflow

Publishing the release will automatically trigger .github/workflows/deploy-to-wp-org.yml, which:

1. Runs the full CI suite to ensure the build isn't broken
2. Installs npm and Composer dependencies
3. Builds JS/CSS assets (npm run build)
4. Copies all plugin files into build/ and update version references (via grunt prepare)
5. Deploys to WP.org SVN via the 10up action — commits to trunk/, creates tags/<version>/, and updates assets/
6. Attaches a .zip of the plugin to the GitHub release

QA notes

• We can try triggering a dry-run by creating a pre-release in GH.