v3.2.0

A plugin's test suites no longer travel with it: php bones deploy leaves them out of the package by default.

bones

• deploy leaves the test suites out (#136). Up to 3.1.0 the default skip list named none of them, so a plugin shipped its tests unless its deploy.php listed them, and --wp, which keeps resources/assets, sent every Jest test in there to WordPress.org with the scripts beside it. Now the package never holds:
  • tests/, phpunit.xml, phpunit.xml.dist and phpunit.dist.xml;
  • jest.config.js and jest.config.json;
  • any __tests__, __snapshots__ or __mocks__ folder, or *.test.* / *.spec.* script (.ts, .tsx, .js, .jsx), outside vendor/ and node_modules/: what the jest.config.js written by migrate:to-v2 runs.
• A package that cannot load is not produced. When the copy's Composer autoloader requires a file the deploy left out — autoload-dev naming a file in tests/, with --keep-dev or with no dev package to prune — the deploy stops and names it, instead of shipping a plugin that fails on every request.

PHPUnit, Brain Monkey and the rest of require-dev were already removed from the package (2.0.7), and the cache PHPUnit writes never shipped.

Upgrading

composer update wpbones/wpbones. Nothing to change. The test entries in your deploy.php become redundant and can stay. To ship one of these paths anyway, take it out with the wpbones_console_deploy_default_skip_files_folders filter.

Docs: What the deploy leaves out

Full Changelog: v3.1.0...v3.2.0