Webship Workspace 1.0.20: the hosting, forge, container-runtime and tracker plugins tell a person without an account, token or command what is missing, and a secret no longer shows in clear. Found by adding each provider plugin to a fresh workspace with no account anywhere. Also new: every plugin can run its own webship-js features in its CI.
Fixed
- A key with the word
secretin its name is a secret: the AWS secret access key is masked in the settings form, the page source andplugins.sh --configure(#431) - A plugin's state says what is missing: "Needs lando" rather than "Ready", and "Needs settings" names the keys still on the placeholder (#433)
- A secret that still holds the placeholder says "not set — still the placeholder" (#439)
- Each plugin's settings form uses only its own labels (#328)
- A quoted settings value is shown without its quotes and saved back quoted (#330)
- A one-line list or map is shown read-only, so typing into it no longer saves a string (#441)
- Settings finds a plugin's description by its package (#435); the
mysqldumpandpg_dumpinstall hints name real packages (#437)
Added
- A reusable workflow that runs a plugin's own webship-js features against a dashboard with the plugin installed from the pull request (#427)
Install or update: npm install -g @webship.co/workspace@1.0.20, then webship-workspace update ~/workspace.