Skip to main content
A registered plugin has no versions until you publish one, and versions come from git tags. When you push a semver tag, the hub builds the plugin from that commit and publishes the version. This guide covers cutting a version and, if you need to, pulling one back.
1

Tag the version and push it

Tag the commit you want to release with a semver tag, prefixed with v, that matches the version in formae-plugin.pkl. Then push the tag.
The tag is what the hub turns into a published version, so it must be a semantic version such as v0.1.0 or v1.2.3.
2

The hub builds and publishes the version

When the tag arrives, the hub builds the plugin from that commit, runs its checks, and publishes the version. A build takes a few minutes. You do not trigger anything else; pushing the tag is the whole action.
3

The version is live

The published version appears on your organization page with its channel and publish time.
The organization page showing the plugin with a published stable version
On the plugin page, the version is now installable with formae plugin install, and the page renders the plugin’s README, supported resources, and license.
The published plugin page with the install command and version details
4

Yank a version to pull it back

If a published version turns out to be broken, yank it. Yanking soft-deletes the version so it can no longer be installed, and it emails the other organization admins an optional reason. Yanking is reversible: unyank restores the version. Confirm the action by typing yank.
The yank confirmation dialog on a published version
A published version’s tag is fixed to the commit it was built from. To ship a fix, publish a new version with a new tag rather than moving the old one. Moving a published tag fails; see Troubleshoot a build.

​
See also