@danielbdev/opencode-go-usage 0.1.0 → 0.1.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.
Files changed (2) hide show
  1. package/README.md +15 -7
  2. package/package.json +6 -1
package/README.md CHANGED
@@ -77,20 +77,28 @@ This package lives in a monorepo of atomic plugins: each package does one thing
77
77
 
78
78
  ## Releasing
79
79
 
80
- Versions are **independent per package**: touching one plugin never forces a release of another.
80
+ A release is cut by pushing a tag shaped `<workspace-directory>@<version>`; GitHub Actions then publishes
81
+ that package through npm trusted publishing (OIDC), so no npm token is stored anywhere.
81
82
 
82
83
  ```sh
83
- npm version patch -w @danielbdev/opencode-go-usage # or minor / major
84
- npm publish -w @danielbdev/opencode-go-usage --access public
84
+ npm version patch -w @danielbdev/opencode-go-usage --no-git-tag-version
85
+ git add packages/go-usage/package.json package-lock.json
86
+ git commit -m "chore(release): go-usage 0.1.1"
87
+ git tag -a go-usage@0.1.1 -m "go-usage 0.1.1"
88
+ git push --follow-tags
85
89
  ```
86
90
 
87
- `--access public` is required on every publish: scoped packages default to private.
91
+ Use an **annotated** tag (`-a`): `git push --follow-tags` only pushes annotated tags, so a lightweight tag
92
+ would silently never trigger the workflow.
93
+
94
+ The workflow checks that the tag matches the version in the manifest, so a mistyped tag fails loudly
95
+ instead of publishing the wrong thing. It runs the tests and the typecheck before publishing, and npm
96
+ attaches a provenance attestation automatically because the repository and the package are public.
88
97
 
89
- `npm publish --workspaces` publishes every package at once, but npm refuses to republish a version that
90
- already exists, so it only fits when every package is bumped together.
98
+ Versions are **independent per package**: touching one plugin never forces a release of another.
91
99
 
92
100
  The repository root stays at `0.0.0` and is never published; it only holds the workspace configuration.
93
- `npm version` also needs a version there, or npm crashes while reading the workspace manifest.
101
+ `npm version` still needs a version there, or npm crashes while reading the workspace manifest.
94
102
 
95
103
  ## Roadmap
96
104
 
package/package.json CHANGED
@@ -1,9 +1,14 @@
1
1
  {
2
2
  "name": "@danielbdev/opencode-go-usage",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "type": "module",
5
5
  "description": "OpenCode V2 plugin that shows the OpenCode Go subscription usage in the session sidebar",
6
6
  "license": "MIT",
7
+ "repository": {
8
+ "type": "git",
9
+ "url": "git+https://github.com/danielbdev/opencode-plugins.git",
10
+ "directory": "packages/go-usage"
11
+ },
7
12
  "keywords": [
8
13
  "opencode",
9
14
  "opencode-plugin",