Prepare v0.2.0 release

Bumps package.json to 0.2.0 and updates the pinned-install examples in
README.md from #v0.1.0 to #v0.2.0. The historical "pre-v0.1.0 build" note
in Troubleshooting stays — it refers to an old cache state, not the
current version.
This commit is contained in:
Wayner Barrios
2026-05-28 13:18:04 -04:00
parent 9a2301e3a3
commit 75351bb816
2 changed files with 3 additions and 3 deletions
+2 -2
View File
@@ -152,7 +152,7 @@ If you already use other plugins (e.g. `superpowers`), keep all of them in the a
To pin a specific tag (recommended once releases exist):
```jsonc
"opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git#v0.1.0"
"opencode-power-pack@git+https://github.com/waybarrios/opencode-power-pack.git#v0.2.0"
```
You still need a local copy of the repo for **step 2** (the slash command files live there). Clone it next to wherever you keep code:
@@ -267,7 +267,7 @@ pkill -f opencode
opencode
```
If you pinned a version in `opencode.json` (e.g. `#v0.1.0`), bump the tag in the JSON before restarting, otherwise OpenCode keeps using the pinned commit.
If you pinned a version in `opencode.json` (e.g. `#v0.2.0`), bump the tag in the JSON before restarting, otherwise OpenCode keeps using the pinned commit.
---
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "opencode-power-pack",
"version": "0.1.0",
"version": "0.2.0",
"description": "Curated bundle of Claude Code skills ported to OpenCode: code-review, feature-dev, security-review, frontend-design, mcp-builder, skill-creator, and the feature-dev sub-agents.",
"type": "module",
"main": ".opencode/plugins/opencode-power-pack.js",