1.0.6

What changed since 1.0.5

Changed

• The workspace no longer describes itself as DDEV-only: the dashboard footer, the folder guides, the norms and the prompts say container-based, with DDEV as the default (#166).
• The guide screenshots that showed the old footer are retaken (#168).

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

1.0.5

What changed since 1.0.4

Fixed

• The Website 12.0.x builder ended with the wrong build function and stopped at "ready to install" (#148).
• The Website builders had no way to ignore a patch or require a package, unlike the other builders (#150).
• A Website build was left on the template's Node.js 20 instead of 24 (#152).
• A stale merge of extra.drupal-recipe-unpack.ignore ran after the lock file was written (#154).
• --template offered three of the five site templates (#156).
• The "Webmaster" test account collided with the installer's webmaster (#158).
• --php-version was lost after create-project (#160).
• Cucumber --add-users failed on a fresh build: the role modules are enabled first (#162).

Core only: no plugin package changed. Install or update: npm install -g @webship.co/workspace@1.0.5, then webship-workspace update ~/workspace.

1.0.4

What changed since 1.0.3

Changed

• The guide's screenshots are retaken on a Webship Workspace dashboard with demo content (#141).

Fixed

• A file opened from a files workspace arrived empty: the route streamed an undefined name (#144).
• A stray image at the root, the avatar file's metadata and one worklog line (#141).

Core only: no plugin changed. Install or update: npm install -g @webship.co/workspace@1.0.4, then webship-workspace update ~/workspace.

1.0.3

What changed since 1.0.2

Fixed

• Every builder aborted: the build function ran composer create-project a second time in the filled folder (#121).
• The testing stack wrote Dockerfile.playwright on every setup and its apt run failed on the web image's PHP repository key (#123).
• cmd-tools-testing.sh --dry-run ran the setup again instead of the dry run (#125).
• The builders never wrote config_sync_directory: the guard matched the commented example in default.settings.php (#129).
• The Webships builder left the template's Node.js 20 in place instead of the workspace's 24 (#131).
• The Webships 3.0.x builder's examples named an --install flag the parser rejects (#133).
• The Webships automated-testing builder failed its theme check on a healthy site (#135).
• cmd-tools-testing.sh --path file.feature:LINE ran no scenario and still said the suite passed (#137).

Added

• Builders in the test workspace for the 12.0.x lines of Webship, Cucumber and Website (#127).

Core only: no plugin changed. Install or update: npm install -g @webship.co/workspace@1.0.3, then webship-workspace update ~/workspace.

1.0.2

What changed since 1.0.1

• Every plugin package is at 1.0.2 as well, released one at a time the way core/docs/releases.md now describes: the version and the sibling ranges bumped, the lock file regenerated and committed with package.json, the registry allowed to serve each package before a dependent was pushed. The CI of the plugins, red since their 1.0.0 commits for exactly those two reasons, is green again (#119).
• A full testing round preceded the release: the dashboard's unit tests (1137 passing), the cmd smoke test (309 passing), the dashboard's own webship-js suite on a live workspace (164 scenarios passing, 9 precondition skips) and every plugin's own test suite.

Install or update: npm install -g @webship.co/workspace@1.0.2, then webship-workspace update ~/workspace and npm update in core/workspace-app.

1.0.1

What changed since 1.0.0

• The NODE and More menus load their bodies when they open, like the other row menus (#111). With the GIT, Graph and IDE plugins at 1.0.1 doing the same, a workspace page of fifty rows is 732 KB instead of 906 KB before compression, and 33 KB instead of 45 KB over the wire.
• CI is green again: the SVG test skips its Claude Code half where the claude CLI is missing (#113), the plugin cycle requires upsun before it activates it (#115), and the core no longer ships graphs/cmd-tools-graphs.sh, which only the graph plugin can run (#117).
• The dashboard's lock file follows js-yaml 5.4.1 (Dependabot).

Install or update: npm install -g @webship.co/workspace@1.0.1.

1.0.0

Webship Workspace 1.0.0: a lean core with a web dashboard, and every feature a plugin.

• Install: npm install -g @webship.co/workspace, then webship-workspace init ~/workspace. The core ships empty; add workspace folders, hosting providers, git forges, container runtimes and features from the Plugins page or webship-workspace plugin require|activate|install|configure <name>.
• 51 plugins at 1.0.0 under @webship.co/workspace-<name>: 26 workspace folders, 7 hosting providers (one base), 3 git forges, 5 container runtimes, git, ide, jira, google-drive, graph.
• Since rc1: the row menus of the core and of the hosting providers load their bodies when they open, so a page of 50 projects is a third of its former size (#107, #109, webship/workspace-hosting#1); the Require box names an npm package (#105).
• The dashboard's own webship-js suite runs green, and scenarios that need a state this machine lacks say so (#100, #103).

1.0.0-rc1

Release candidate 1 of the Webship Workspace: the core and every plugin at 1.0.0-rc1.

Since beta2:

• Scenarios that need a state say so and skip with the reason: @needs-testing-stack, @needs-running-project, and @needs-setting-<plugin>-<key> for a plugin's own feature (#100, #103).
• The clone scenarios take the first project of the dev workspace and name no project of one machine (#100).
• Six unit tests build the tree they read; the unit suite passes on a clean clone (#92).
• Jira plugin: a malformed key is refused before the folder is looked up (webship/workspace-jira#3).

Install: npm install -g @webship.co/workspace then webship-workspace init ~/workspace.

1.0.0-beta2

Beta 2 of the Webship Workspace core.

• The dashboard starts again: four core modules no longer require the graphs module that moved to the graph plugin (#91).
• Install the workspace with npm: npm install -g @webship.co/workspace, webship-workspace init, a plugin catalogue on the Plugins page and in webship-workspace catalog; the core ships empty (#84).
• js-yaml 5.4.1 (#94).
• The webship-js suite's settings and row scenarios follow the pages as they are (#96, #98).
• A unit test loads every core module, so a dangling require fails the suite instead of the first start.

Every plugin is @webship.co/workspace-<name>; the workspace-folder plugins are at 1.0.0-beta2 with their features fixed, the rest at 1.0.0-beta1.