Skip to content

1.0.23

Choose a tag to compare

@Natshah Natshah released this 19 Nov 20:47
· 191 commits to 1.0.x since this release
5ef5698

What changed since 1.0.22

Prove a step pack before it is on npm, take a plugin out for good, and a testing setup that says when it failed.

Added

  • cmd-tools-testing.sh <project> --add-steps takes a step pack's tarball (what npm pack makes) or its folder as well as its name. The pack can then be proven on a real project before its release (#491, #499):

    • the tarball is copied into the project's tests/step-packs/, where the project's container sees it, and devDependencies points there;
    • a rebuilt tarball replaces the one before it and is installed again;
    • it never replaces the same pack from npm;
    • --remove-steps deletes the copied tarball with the rest.
  • bash core/scripts/plugins.sh --remove <name> (and webship-workspace plugin remove <name>) is the last step back after --uninstall (#493, #502):

    • the plugin's package leaves the dashboard;
    • plugins.<name> leaves settings.yml;
    • its settings file stays.

    On Settings → Plugins, a plugin that is not active and placed nothing has a Remove button.

  • The list of step packs shipped with the core knows the seven packs released on 2026-11-19, with their logos (#495, #496, #500, #501, #503, #504): Laravel, Symfony, CodeIgniter, Bootstrap, WooCommerce (an extension of the WordPress pack), Shopify and MediaWiki. Setting testing up on a wiki suggests the MediaWiki pack.

Fixed

  • The testing setup (cmd-tools-testing.sh <project>) stops with a failure when the project's npm install fails. Before, it said "Testing is set up" over a project with no webship-js (#492, #497).
  • An AI item a plugin placed is titled with the casing of the plugin's label: "WooCommerce Tester", not "Woocommerce Tester" (#494, #498).

Install or update: npm install -g @webship.co/workspace@1.0.23, then webship-workspace update ~/workspace.