-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #852 from publishpress/release-v2.12.0
Release v2.12.0
- Loading branch information
Showing
123 changed files
with
11,818 additions
and
2,215 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,108 @@ | ||
| # A set of files you probably don't want in your WordPress.org distribution | ||
| *.code-workspace | ||
| *.sql | ||
| *.tar.gz | ||
| *.zip | ||
| .DS_Store | ||
| .babelrc | ||
| .distignore | ||
| .editorconfig | ||
| .env.testing | ||
| .env.testing.dist | ||
| .env.testing.linux.dist | ||
| .env.testing.mac.dist | ||
| .eslintrc.js | ||
| .git | ||
| .git | ||
| .gitattributes | ||
| .github | ||
| .gitignore | ||
| .idea | ||
| .php-cs-fixer.cache | ||
| .phpcs.xml | ||
| .phplint-cache | ||
| .phplint.yml | ||
| .rsync-filters-post-build | ||
| .rsync-filters-pro-build | ||
| .travis.yml | ||
| .vscode | ||
| .wordpress-org | ||
| /assets_wp | ||
| /dev-workspace | ||
| /dist | ||
| /version.txt | ||
| /webpack.config.js | ||
| /yarn.lock | ||
| CONTRIBUTING.md | ||
| Gruntfile.js | ||
| README-build.md | ||
| README.md | ||
| RoboFile.php | ||
| Thumbs.db | ||
| /assets/jsx | ||
| /assets_wp | ||
| bin | ||
| bin | ||
| build.xml | ||
| builder | ||
| builder.yml | ||
| builder.yml.dist | ||
| codeception.dist.yml | ||
| composer.json | ||
| composer.lock | ||
| cs | ||
| cypress | ||
| cypress.json | ||
| /dist | ||
| jest.config.js | ||
| jest.config.ts | ||
| jsconfig.json | ||
| mix-manifest.json | ||
| node_modules | ||
| package-lock.json | ||
| package.json | ||
| phpcs.xml | ||
| phpunit.xml | ||
| psalm.xml | ||
| ray-dist.php | ||
| ray.php | ||
| screenshot-*.png | ||
| /scripts | ||
| tailwind.config.js | ||
| tests | ||
| vendor | ||
| vendor/bin | ||
| vendor/pimple/pimple/.gitignore | ||
| vendor/pimple/pimple/.php_cs.dist | ||
| vendor/pimple/pimple/CHANGELOG | ||
| vendor/pimple/pimple/README.rst | ||
| vendor/pimple/pimple/composer.json | ||
| vendor/pimple/pimple/ext | ||
| vendor/pimple/pimple/ext/pimple/.gitignore | ||
| vendor/pimple/pimple/phpunit.xml.dist | ||
| vendor/pimple/pimple/src/Pimple/Tests | ||
| vendor/psr/container/.gitignore | ||
| vendor/psr/container/composer.json | ||
| vendor/publishpress/publishpress-instance-protection/.git | ||
| vendor/publishpress/publishpress-instance-protection/.gitattributes | ||
| vendor/publishpress/publishpress-instance-protection/.gitignore | ||
| vendor/publishpress/vendor-locator-series/composer.json | ||
| vendor/publishpress/wordpress-banners/.gitattributes | ||
| vendor/publishpress/wordpress-reviews/phpcs.xml.dist | ||
| vendor/publishpress/wordpress-version-notices/.gitignore | ||
| vendor/publishpress/wordpress-version-notices/README.md | ||
| vendor/publishpress/wordpress-version-notices/bin | ||
| vendor/publishpress/wordpress-version-notices/codeception.dist.yml | ||
| vendor/publishpress/wordpress-version-notices/codeception.yml | ||
| vendor/publishpress/wordpress-version-notices/tests | ||
| vendor/sabre/vobject/.gitignore | ||
| vendor/sabre/vobject/README.md | ||
| vendor/sabre/vobject/bin | ||
| vendor/sabre/vobject/composer.json | ||
| vendor/sabre/vobject/tests | ||
| vendor/symfony/polyfill-ctype/README.md | ||
| vendor/symfony/polyfill-ctype/composer.json | ||
| vendor/woocommerce/action-scheduler/README.md | ||
| vendor/woocommerce/action-scheduler/changelog.txt | ||
| webpack.config.js | ||
| webpack.mix.js |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,16 +1,62 @@ | ||
| .github export-ignore | ||
| assets_wp export-ignore | ||
| tests export-ignore | ||
| *.bash export-ignore | ||
| *.cache export-ignore | ||
| *.code-workspace export-ignore | ||
| *.dist export-ignore | ||
| *.dist.yml export-ignore | ||
| *.exe export-ignore | ||
| *.sh export-ignore | ||
| *.sql export-ignore | ||
| *.tar.gz export-ignore | ||
| *.testing export-ignore | ||
| *.zip export-ignore | ||
| .DS_Store export-ignore | ||
| .babelrc export-ignore | ||
| .env.testing.dist export-ignore | ||
| .distignore export-ignore | ||
| .editorconfig export-ignore | ||
| .git export-ignore | ||
| .gitattributes export-ignore | ||
| .github export-ignore | ||
| .gitignore export-ignore | ||
| .gitlab-ci.yml export-ignore | ||
| .phpcs.xml export-ignore | ||
| .phplint.yml export-ignore | ||
| codeception.dist.yml export-ignore | ||
| composer.json export-ignore | ||
| composer.lock export-ignore | ||
| package.json export-ignore | ||
| package-lock.json export-ignore | ||
| .rsync-filters-post-build export-ignore | ||
| .rsync-filters-pre-build export-ignore | ||
| .travis.yml export-ignore | ||
| .vscode export-ignore | ||
| /assets_wp export-ignore | ||
| /dev-workspace export-ignore | ||
| /dist export-ignore | ||
| /screenshot-*.png export-ignore | ||
| /tests export-ignore | ||
| Gruntfile.js export-ignore | ||
| Gruntfile.js export-ignore | ||
| README.md export-ignore | ||
| RoboFile.php export-ignore | ||
| Thumbs.db export-ignore | ||
| behat.yml export-ignore | ||
| bin export-ignore | ||
| builder.yml export-ignore | ||
| circle.yml export-ignore | ||
| codeception.yml export-ignore | ||
| docker-compose.yml export-ignore | ||
| jest.config.js export-ignore | ||
| jest.config.ts export-ignore | ||
| jsconfig.json export-ignore | ||
| multisite.xml export-ignore | ||
| multisite.xml.dist export-ignore | ||
| node_modules export-ignore | ||
| package-lock.json export-ignore | ||
| package.json export-ignore | ||
| phpcs.ruleset.xml export-ignore | ||
| phpcs.xml export-ignore | ||
| phpcs.xml.dist export-ignore | ||
| phpmd.xml export-ignore | ||
| phpunit.xml export-ignore | ||
| phpunit.xml.dist export-ignore | ||
| psalm.xml export-ignore | ||
| webpack.config.js export-ignore | ||
| .gitattributes export-ignore | ||
| .git export-ignore | ||
| wp-cli.local.yml export-ignore | ||
| webpack.common.js export-ignore | ||
| webpack.dev.js export-ignore | ||
| webpack.prod.js export-ignore |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,34 +1,43 @@ | ||
| --- | ||
| name: Release the Free version (team only) | ||
| about: Describes default checklist for the plugin's release process. | ||
| title: Release v[VERSION] | ||
| name: Release the Free Version (Team Only) | ||
| about: Default checklist for the plugin's release process. | ||
| title: Release PublishPress Series v[VERSION] | ||
| labels: release | ||
| assignees: '' | ||
| --- | ||
|
|
||
| To release the Free plugin please make sure to check all the checkboxes below. | ||
| To release the Free plugin, ensure you complete all the tasks below. | ||
|
|
||
| ### Pre-release Checklist | ||
| - [ ] Create the release branch as `release-<version>` based on the development branch. | ||
| - [ ] Make sure to directly merge or use Pull Requests to merge hotfixes or features branches into the release branch. | ||
| - [ ] Run `composer update --no-dev --dry-run` and check if there is any relevant update on any requirement. This won't change the code, just show a simulation of running the update command. Evaluate the need of releasing with this library updated, or if we can add that for a next release. | ||
| - [ ] If any update should be included on this release (from previous step) make sure to run the update command only for the specific dependeny: `composer update the/lib:version-constraint`. Make sure to check compatibility with the plugin and what version we should be using. Check if you need to lock the current version for any dependency using exact version numbers instead of relative version constraints. Make sure to add any change of dependencies to the changelog. | ||
| - [ ] Check Github's Dependabot warnings or pull requests, looking for any relevant report. Remove any false-positive first. Fix and commit the fix for the issues you find. | ||
| - [ ] Build JS files to production running `composer build:js` and commit (if your plugin uses any compiled JS file). | ||
| - [ ] Run WP VIP scan to make sure no warnings or errors > 5 exists: `composer phpcs`. | ||
| - [ ] Update the changelog - make sure all the changes are there with a user-friendly description and that the release date is correct. | ||
| - [ ] Update the version number to the next stable version in the main plugin file and `readme.txt`. Commit the changes to the release branch. | ||
| - [ ] Commit the changes to the release branch. | ||
| - [ ] Build the zip package, running `composer build`. It should create a package in the `./dist` dir. | ||
| - [ ] Send the new package to the team for testing. | ||
| - [ ] Create a release branch named `release-<version>` from the development branch. | ||
| - [ ] Review and merge all relevant Pull Requests into the release branch. | ||
| - [ ] Start a dev-workspace session. | ||
| - [ ] Execute `composer update` to update the root and lib vendors. | ||
| - [ ] Review the updated packages. Mention any production library updates in the changelog. | ||
| - [ ] Inspect GitHub's Dependabot warnings or Pull Requests for relevant issues. Resolve any false positives first, then fix and commit the remaining issues. | ||
| - [ ] If necessary, build JS files for production using `composer build:js` and commit the changes. | ||
| - [ ] 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. | ||
| - [ ] 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. | ||
| - [ ] Revise the changelog to include all changes with user-friendly descriptions and ensure the release date is accurate. | ||
| - [ ] Update the version number in the main plugin file and `readme.txt`, adhering to specifications from our [tech documentation](https://rambleventures.slab.com/posts/version-numbers-58nmrk4b), and commit to the release branch. | ||
| - [ ] Confirm there are no uncommitted changes. | ||
| - [ ] Build the zip package with `composer build`, creating a new package in the `./dist` directory. | ||
| - [ ] Distribute the new package to the team for testing. | ||
|
|
||
| ### Release Checklist | ||
| - [ ] Create a Pull Request and merge the release branch it into the `master` branch. | ||
| - [ ] Merge the `master` branch into the `development` branch. | ||
| - [ ] Create the GitHub release (make sure it is based on the `master` branch and correct tag). This will trigger a Github action for automatic deployment on the WordPress SVN repo. | ||
| - [ ] Create and merge a Pull Request for the release branch into the `main` branch. | ||
| - [ ] Merge the `main` branch into the `development` branch. | ||
| - [ ] Establish the GitHub release on the `main` branch with the correct tag. | ||
|
|
||
| ### Post-release Checklist | ||
|
|
||
| - [ ] Follow the action's result on the [repository actions page](https://github.com/publishpress/publishpress-series/actions). | ||
| - [ ] Go to the [WordPress.org plugin page](https://wordpress.org/plugins/organize-series/) double check the information confirming the release finished successfully. | ||
| - [ ] Make a final test updating the plugin in a staging site. | ||
| #### WP SVN Deployment | ||
| - [ ] Navigate to the local copy of the SVN repo for the plugin. | ||
| - [ ] Update your working copy using `svn update`. | ||
| - [ ] Clear the `trunk` directory with `rm -rf trunk/*`. | ||
| - [ ] Unzip the built package and transfer files to the `trunk` folder. | ||
| - [ ] Remove any extraneous files (if found, create an issue to amend the `.rsync-filter-post-build` file). Keep only files really used on production. | ||
| - [ ] Find new files with `svn status | grep \?` and add them using `svn add <each_file_path>`. | ||
| - [ ] Identify removed files with `svn status | grep !` and delete them using `svn rm <each_file_path>`. | ||
| - [ ] Create the new tag using `svn cp trunk tags/<version>`. | ||
| - [ ] Commit the changes with `svn ci -m 'Releasing <version>'`. | ||
| - [ ] Await WordPress's version number update and perform a final test by updating the plugin on a staging site. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,39 +1,38 @@ | ||
| --- | ||
| name: Release the Pro version (team only) | ||
| about: Describes default checklist for releasing the Pro plugin; | ||
| title: Release Pro v[VERSION] | ||
| name: Release the Pro Version (Team Only) | ||
| about: Default checklist for the plugin's release process. | ||
| title: Release PublishPress Series Pro v[VERSION] | ||
| labels: release | ||
| assignees: '' | ||
| --- | ||
|
|
||
| To release the Pro plugin please make sure to check all the checkboxes below. | ||
| To release the Pro plugin, ensure you complete all the tasks below. | ||
|
|
||
| ### Pre-release Checklist | ||
|
|
||
| - [ ] Create the release branch as `release-<version>` based on the development branch. | ||
| - [ ] Make sure to directly merge or use Pull Requests to merge hotfixes or features branches into the release branch. | ||
| - [ ] Run `composer update --no-dev --dry-run` and check if there is any relevant update on any requirement. This won't change the code, just show a simulation of running the update command. Evaluate the need of releasing with this library updated, or if we can add that for a next release. | ||
| - [ ] If any update should be included on this release (from previous step) make sure to run the update command only for the specific dependeny: `composer update the/lib:version-constraint`. Make sure to check compatibility with the plugin and what version we should be using. Check if you need to lock the current version for any dependency using exact version numbers instead of relative version constraints. Make sure to add any change of dependencies to the changelog. | ||
| - [ ] Check Github's Dependabot warnings or pull requests, looking for any relevant report. Remove any false-positive first. Fix and commit the fix for the issues you find. | ||
| - [ ] Build JS files to production running `composer build:js` and commit (if your plugin uses any compiled JS file). | ||
| - [ ] Run WP VIP scan to make sure no warnings or errors > 5 exists: `composer phpcs`. | ||
| - [ ] Update the changelog - make sure all the changes are there with a user-friendly description and that the release date is correct. | ||
| - [ ] Update the version number to the next stable version in the main plugin file and `readme.txt`. Commit the changes to the release branch. | ||
| - [ ] Commit the changes to the release branch. | ||
| - [ ] Build the zip package, running `composer build`. It should create a package in the `./dist` dir. | ||
| - [ ] Send the new package to the team for testing. | ||
| - [ ] Create a release branch named `release-<version>` from the development branch. | ||
| - [ ] Review and merge all relevant Pull Requests into the release branch. | ||
| - [ ] Start a dev-workspace session. | ||
| - [ ] Verify the correct version of the free plugin is referenced in the `lib/composer.json` file. Prefer stable versions. | ||
| - [ ] Execute `composer update` to update the root and lib vendors. | ||
| - [ ] Review the updated packages and mention any production library updates in the changelog. | ||
| - [ ] 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. | ||
| - [ ] 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. | ||
| - [ ] Inspect GitHub's Dependabot warnings or Pull Requests for relevant issues. Resolve any false positives first, then fix and commit the remaining issues. | ||
| - [ ] If necessary, build JS files for production using `composer build:js` and commit the changes. | ||
| - [ ] 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. | ||
| - [ ] 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. | ||
| - [ ] Revise the changelog to include all changes with user-friendly descriptions and ensure the release date is accurate. | ||
| -- [ ] Update the version number in the main plugin file and `readme.txt`, adhering to specifications from our [tech documentation](https://rambleventures.slab.com/posts/version-numbers-58nmrk4b), and commit to the release branch. | ||
| - [ ] Confirm there are no uncommitted changes. | ||
| - [ ] Build the zip package with `composer build`, creating a new package in the `./dist` directory. | ||
| - [ ] Distribute the new package to the team for testing. | ||
|
|
||
| ### Release Checklist | ||
| - [ ] Create and merge a Pull Request for the release branch into the `main` branch. | ||
| - [ ] Merge the `main` branch into the `development` branch. | ||
| - [ ] Establish the GitHub release on the `main` branch with the correct tag. | ||
|
|
||
| - [ ] Create a Pull Request and merge the release branch it into the `master` branch. | ||
| - [ ] Merge the `master` branch into the `development` branch. | ||
| - [ ] Create the Github release (make sure it is based on the `master` branch and correct tag). | ||
| - [ ] Follow the action's result on the [repository actions page](https://github.com/publishpress/publishpress-series-pro/actions). | ||
| - [ ] Go to [PublishPress site admin panel](https://publishpress.com/wp-admin) > Downloads, locate "Series Pro", and edit: | ||
| - [ ] File URL on Download Files, uploading the new package to the media library. | ||
| - [ ] On Licensing, update the version number. | ||
| - [ ] On Licensing, update the changelog. | ||
|
|
||
| ### Post-release Checklist | ||
|
|
||
| - [ ] Make the final test updating the plugin in a staging site. | ||
| #### PublishPress.com Deployment | ||
| - [ ] Update the EDD registry on the Downloads menu, uploading the new package. | ||
| - [ ] Perform a final test by updating the plugin on a staging site. |
Oops, something went wrong.