WP Bones 2.0.10 is out a safety release for bones, the CLI every WP Bones plugin carries, after I audited it line by line
deploy checks where it deploys. php bones deploy .. used to delete every plugin beside yours, and then yours. Now the plugin, its parents and anything inside it are refused, and an unrelated folder needs --force.
WP Bones 2.0.9 is out a small one, about numbers that had quietly stopped agreeing
bones version keeps its hands off your dependencies. On an npm 6 lockfile (lockfileVersion: 1) it bumped your plugin and the first package in the tree. Now only your plugin's own entry moves.
WP Bones 2.0.8 is out and it started as a community pull request
$this->plugin in your commands. Custom php bones commands that call $this->loadWordPress() now get your plugin instance: its config, its services, everything it registers. Before, the loader looked in the framework's own folder and your plugin never booted.
WP Bones 2.0.7 is out and it's a quiet one that makes every release you ship lighter.
Dev packages stay home. bones deploy used to copy vendor/ exactly as it was on disk so PHPUnit, Brain Monkey and everything a test suite pulls in went into your plugin package. On one of my own plugins that was 31 packages. Now the deploy prunes them in the copy, against your composer.lock, and never touches your working tree. Want them anyway? --keep-dev.
Hey everyone! WPBones v2.0 just dropped the biggest release since the framework launched. Here s the short version:
The old build pipeline is gone. No more Gulp, no more run-s, no more per-plugin build scripts that drift over time. v2 replaces everything with a single webpack.config.js that auto-discovers your entries from resources/assets/. Drop a .tsx file, webpack picks it up. That s it.
