Release a workspace plugin

For: plugin authors.

Install a workspace revision or export it to Git.

Install and roll out

The Release task says which revision is the folder's head and which is installed. Install revision installs the head, or the revision you are looking at, exactly as plugin install workspace:<folder>@<revision> does from the CLI:

• the plugin's checks run first, and a revision with errors is refused;
• a version with evals runs them on a test node first, and the panel shows the quality gate's verdict with each eval's result;
• when two or more nodes run the plugin, the new version goes to a canary first and then to the rest in steps, and the panel follows the rollout step by step.

Export to Git

Under the install panel, Export to Git pushes the head, or the revision you are looking at, to a repository as a new branch, exactly as workspace export does from the CLI (Export to Git).

Give the repository's https:// URL, and optionally the new branch's name (oz0/<folder>-<revision> by default), the branch it starts from, the folder of the repository the plugin goes into, and the tenant secret with a token that may push; the token never reaches the browser, only its secret's name. Open a pull request opens one on GitHub, Gitea or Forgejo, or a merge request on GitLab, with the forge and its API for a self-hosted one, and a title and description (the revision's message by default). The panel then shows the branch, the commit and a link to the pull request.

A branch that exists is refused, and the dialog says so. Admins and owners may export; every export is in the audit log.