plugin-release
Installation
SKILL.md
English | 简体中文
plugin-release
Ship developed, tested plugins safely. Publishing is a one-way outbound action — show a plan and obtain confirmation before any actual publish or tag push; this skill does not decide version numbers for you, and it never bumps versions automatically.
Step 0: confirm the target version and release track
| Release track | Applies to | Key facts |
|---|---|---|
| GitHub direct install | dsh plugin --profile <p> add github:owner/repo |
Consumers resolve the default-branch HEAD; publishing = pushing to main — run the full gate before pushing |
| npm registry | npm publish |
Official release line only; alpha/rc-prefixed @deepseek-ai/* versions are not guaranteed on npm — verify with npm view <pkg> versions before publishing |
| hub listing | register in the hub catalog | Registration is a separate action and does not replace packaging validation |
| collection | member plugins vendored into a pack artifact | Follow the owning collection repository's own process |
The unpublished cohort (for example a cohort version that was never published to npm — alpha.1 was GitHub-only; alpha.2 through alpha.4 are published under the alpha dist-tag) goes through the overrides flow in references/publish-playbook.md. Do not look for versions that do not exist on npm, and do not switch package managers because of it.