@asermax/pi-tentacles 0.1.0 → 1.1.0

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 (5) hide show
  1. package/README.md +6 -5
  2. package/extension/index.js +699 -26
  3. package/package.json +1 -1
  4. package/skills/tentacles/SKILL.md +20 -2
  5. package/tentacles-helper +8111 -135
package/README.md CHANGED
@@ -41,11 +41,12 @@ A setting the agent passes to `spawn` wins over its variable.
41
41
 
42
42
  `pnpm build` bundles the helper, the pi extension and the Claude mod with vite, then `build/emit.ts` lays out both plugins with their manifests and the skill.
43
43
 
44
- ## Publish
44
+ ## Release
45
45
 
46
- The version is the `version` in `apps/plugin/package.json`; the build writes it into both manifests and the marketplace entry.
46
+ The version is the content of the `VERSION` file at the repository root; the build writes it into both manifests and the marketplace entry. Nobody edits it: on every push to `master`, CI runs semantic-release (config in `.releaserc.json`), which picks the next version from the conventional commits since the last `v*` tag (`fix` is a patch, `feat` a minor, a breaking change a major; other types release nothing), writes it to `VERSION`, rebuilds, and then:
47
47
 
48
- - **pi package**: CI runs `scripts/publish-npm.sh` on every push to `master`. The script builds the plugin and publishes `build/out/pi` to npm with provenance when npm has no `@asermax/pi-tentacles` at that version. To release, bump the version. The script authenticates with one of these, set up once:
49
- - **Trusted publisher**: on npmjs.com, open the package's Settings, then Trusted publishing. Add GitHub Actions with user `asermax`, repository `tentacles`, workflow filename `ci.yml` and no environment. Allow both `npm publish` and `npm stage publish`. npm offers trusted publishing only for a package that already exists, so the first version needs the token below or a manual `npm publish` from `build/out/pi`.
48
+ - **pi package**: publishes `build/out/pi` to npm with provenance. npm authenticates with one of these, set up once:
49
+ - **Trusted publisher**: on npmjs.com, open the package's Settings, then Trusted publishing. Add GitHub Actions with user `asermax`, repository `tentacles`, workflow filename `ci.yml` and no environment. Allow both `npm publish` and `npm stage publish`. npm offers trusted publishing only for a package that already exists.
50
50
  - **Token**: a granular npm access token with publish rights on the package, stored as the repository secret `NPM_TOKEN`. When both are set up, npm uses the trusted publisher.
51
- - **Claude plugin**: CI runs `scripts/publish-marketplace.sh` on every push to `master`. The script builds the plugin and force-pushes it as the root of the orphan `claude-marketplace` branch. `scripts/publish-marketplace.sh /path/to/bare.git` pushes the same branch to a local bare repository instead of `origin`.
51
+ - **Claude plugin**: runs `scripts/publish-marketplace.sh <version>`, which force-pushes `build/out/claude` as the root of the orphan `claude-marketplace` branch. `scripts/publish-marketplace.sh <version> /path/to/bare.git` pushes the same branch to a local bare repository instead of GitHub; run `pnpm build` first.
52
+ - **Repository**: commits `VERSION` and `CHANGELOG.md` to `master` with `[skip ci]`, creates the `v<version>` tag and the GitHub release.