Webship Workspace 1.0.23 lets you prove a Webship-js step pack on a real project before it is on npm, takes a plugin out of a workspace for good, and says when setting testing up fails. Its list of step packs knows the seven packs released on 19 November 2026.
Added
cmd-tools-testing.sh <project> --add-stepstakes a step pack's tarball (whatnpm packmakes) or its folder as well as its name (#491):- the tarball is copied into the project's
tests/step-packs/, where the project's container sees it; - a rebuilt tarball replaces the one before it and is installed again;
- it never replaces the same pack from npm, and
--remove-stepsdeletes the copy with the rest.
- the tarball is copied into the project's
bash core/scripts/plugins.sh --remove <name>, and a Remove button on Settings → Plugins: after--uninstall, the plugin's package leaves the dashboard and its line leavessettings.yml. Its settings file stays (#493)- The list of step packs the core ships knows Laravel, Symfony, CodeIgniter, Bootstrap, WooCommerce, Shopify and MediaWiki, with their logos. Setting testing up on a wiki suggests the MediaWiki pack (#495, #500, #503)
Fixed
- Setting testing up (
cmd-tools-testing.sh <project>) stops with a failure when the project'snpm installfails, instead of saying "Testing is set up" (#492) - An AI item a plugin placed is titled with the casing of the plugin's label: "WooCommerce Tester", not "Woocommerce Tester" (#494)
Install or update: npm install -g @webship.co/workspace@1.0.23, then webship-workspace update ~/workspace.