Skip to content

1.0.20

Latest

Choose a tag to compare

@Natshah Natshah released this 17 Nov 02:54
e9c1f58

What changed since 1.0.19

From testing round 9: every hosting, forge, container-runtime and tracker plugin added by a person who has no account, no token or no CLI for it.

Fixed

  • A key with the word secret in its name is a secret: the AWS secret access key is masked in the settings form, the page source and plugins.sh --configure (#431).
  • A plugin's state says what is missing: "Needs lando" (the command) 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", and the raw editor shows it (#439).
  • A plugin's settings file is labelled by that plugin only: GoDaddy's form no longer reads "Acquia API key", GitLab and Bitbucket no longer carry GitHub's hints (#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 in the form, so typing into it no longer saves a string (#441).
  • Settings finds a plugin's catalogue line by its package: Google Drive no longer says "No description" (#435).
  • The install hint of mysqldump and pg_dump names their client packages (#437).

Added

  • A reusable workflow, .github/workflows/plugin-browser-suite.yml: a plugin's CI calls it to run the 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.