Prepare the plugin for deployment to WordPress.org via automated GitHub Actions workflow.
- •
Run production build
- •Execute
npm run build - •Verify build completes without errors
- •Execute
- •
Update version numbers
- •Ask user for new version number (e.g., "1.2.0")
- •Update
package.jsonversion - •Update
designsetgo.phpheader "Version:" field (line 6) - •Update
designsetgo.phpDESIGNSETGO_VERSION constant (line 25) - •Update
readme.txt"Stable tag:" field - •Add new version entry to changelog in
readme.txt
- •
Run security audit
- •Execute
/security-auditcommand - •Address any critical or high severity issues
- •Execute
- •
Run tests and lint
- •Execute
npm testto ensure all tests pass - •Execute
npm run lint:jsandnpm run lint:css - •Fix any issues found
- •Execute
- •
Pre-deployment checklist
- •Do we need to update any documentation?
- •All tests passing?
- •No console errors in browser (editor + frontend)?
- •Works with latest WordPress version?
- •Works with latest Gutenberg plugin?
- •Tested with common themes (esp. Twenty Twenty-Five)?
- •Security audit clean?
- •Changelog updated?
- •Screenshots current in
.wordpress-org/? - •readme.txt description under 150 characters?
- •
Commit and tag for deployment
- •Stage all changes:
git add . - •Commit:
git commit -m "chore: Release version X.X.X" - •Create tag:
git tag vX.X.X - •Push commits:
git push origin main - •Push tag:
git push origin vX.X.X - •GitHub Actions will automatically deploy to WordPress.org SVN
- •Stage all changes:
- •
Verify deployment
- •Monitor GitHub Actions workflow at https://github.com/jnealey88/designsetgo/actions
- •Wait 5-10 minutes for WordPress.org to process
- •Check plugin page: https://wordpress.org/plugins/designsetgo/
- •Verify version number, changelog, and screenshots display correctly
Note: The .distignore file controls which files are excluded from WordPress.org deployment. Only production files from /build/ are included; development files (/src/, /tests/, .github/, etc.) are automatically excluded.