opencode-effect-enforcer 0.2.0 → 0.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -21,7 +21,7 @@ That is the complete installation. OpenCode resolves published package entries
|
|
|
21
21
|
for you; there is no separate `npm install` step. Use the global config at
|
|
22
22
|
`~/.config/opencode/opencode.jsonc` to enable it everywhere, or a project config
|
|
23
23
|
to enable it only for that project. You can also pin a release, for example
|
|
24
|
-
`"opencode-effect-enforcer@0.2.
|
|
24
|
+
`"opencode-effect-enforcer@0.2.1"`.
|
|
25
25
|
|
|
26
26
|
Start a new OpenCode session, then verify the plugin if needed:
|
|
27
27
|
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "https://www.schemastore.org/package.json",
|
|
3
3
|
"name": "opencode-effect-enforcer",
|
|
4
|
-
"version": "0.2.
|
|
4
|
+
"version": "0.2.1",
|
|
5
5
|
"description": "OpenCode V2 plugin for Effect v4 skills, guidance, and pattern enforcement",
|
|
6
6
|
"keywords": [
|
|
7
7
|
"opencode",
|
|
@@ -17,7 +17,7 @@
|
|
|
17
17
|
"author": "Marc Suesser",
|
|
18
18
|
"repository": {
|
|
19
19
|
"type": "git",
|
|
20
|
-
"url": "https://github.com/mpsuesser/opencode-effect-enforcer.git"
|
|
20
|
+
"url": "git+https://github.com/mpsuesser/opencode-effect-enforcer.git"
|
|
21
21
|
},
|
|
22
22
|
"publishConfig": {
|
|
23
23
|
"access": "public"
|