PublishPress Blocks adds the missing blocks and configuration you need to build professional websites. Take the control of the new Gutenberg editor with user edition profile configuration and 20+ new blocks and options.
To release the Pro plugin, ensure you complete all the tasks below.
Pre-release Checklist
[x] Create a release branch named release-3.2.1 from the development branch.
[x] Review and merge all relevant Pull Requests into the release branch.
[x] Start a dev-workspace session.
[x] Verify the correct version of the free plugin is referenced in the lib/composer.json file. Prefer stable versions.
[x] Execute composer update to update the root and lib vendors.
[x] Review the updated packages and mention any production library updates in the changelog.
[x] Check if all dependencies are synced from Free into the Pro plugin with composer check:deps. If required, merge dependencies using composer fix:deps and run composer update again.
[x] Check if the free plugin uses Composer's autoload and copy the autoload definition from the free plugin to the pro plugin refactoring the relative paths, on /lib/composer.json. Execute composer dumpautoload to update the autoload files. Commit the changes.
[ ] #1353
[x] If necessary, build JS files for production using composer build:js and commit the changes.
[x] Run a WP VIP scan with composer check:phpcs to ensure no warnings or errors greater than 5 exist.
[ ] Update the .pot file executing composer gen:pot and include a note in the changelog.
[x] Especially for minor and patch releases, maintain backward compatibility for changes like renamed or moved classes, namespaces, functions, etc. Include deprecation comments and mention this in the changelog. Major releases may remove deprecated code, but always note this in the changelog.
[x] Revise the changelog to include all changes with user-friendly descriptions and ensure the release date is accurate.
[x] Update the version number in the main plugin file and readme.txt, adhering to specifications from our tech documentation, and commit to the release branch.
[x] Confirm there are no uncommitted changes.
[x] Build the zip package with composer build, creating a new package in the ./dist directory.
[x] Distribute the new package to the team for testing.
Release Checklist
[x] Create and merge a Pull Request for the release branch into the main branch.
[x] Merge the main branch into the development branch.
[x] Establish the GitHub release on the main branch with the correct tag.
PublishPress.com Deployment
[x] Update the EDD registry on the Downloads menu, uploading the new package.
[x] Perform a final test by updating the plugin on a staging site.
To release the Pro plugin, ensure you complete all the tasks below.
Pre-release Checklist
release-3.2.1from the development branch.lib/composer.jsonfile. Prefer stable versions.composer updateto update the root and lib vendors.composer check:deps. If required, merge dependencies usingcomposer fix:depsand runcomposer updateagain./lib/composer.json. Executecomposer dumpautoloadto update the autoload files. Commit the changes.composer build:jsand commit the changes.composer check:phpcsto ensure no warnings or errors greater than 5 exist..potfile executingcomposer gen:potand include a note in the changelog.readme.txt, adhering to specifications from our tech documentation, and commit to the release branch.composer build, creating a new package in the./distdirectory.Release Checklist
mainbranch.mainbranch into thedevelopmentbranch.mainbranch with the correct tag.PublishPress.com Deployment