@nithin554/code-crawler 0.1.75 → 0.1.76
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 +11 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -307,13 +307,20 @@ plugin is published there too:
|
|
|
307
307
|
`plugins/code-crawler/package.json` is packaging metadata — ClawHub needs a package
|
|
308
308
|
manifest to inspect the bundle and build its ClawPack artifact, and warns when one is
|
|
309
309
|
missing — so the release workflow stamps the tag's version into it, packs the bundle, and
|
|
310
|
-
|
|
310
|
+
publishes that tarball; the committed `version` is only a placeholder.
|
|
311
311
|
|
|
312
|
-
|
|
312
|
+
The plugin publish runs the official `clawhub` CLI itself, under Node, rather than calling
|
|
313
|
+
upstream's reusable `package-publish.yml`. That workflow cannot publish this bundle: it
|
|
314
|
+
inspects the packed artifact with `bun ... package validate`, and the CLI refuses to run under
|
|
315
|
+
Bun ("Plugin validation requires Node.js 22.13+ (22.x) or 24+"). A ClawPack always contains
|
|
316
|
+
`package/package.json` and no input skips the step, so the call only ever succeeded while the
|
|
317
|
+
bundle had no manifest — the very thing ClawHub warns about.
|
|
318
|
+
|
|
319
|
+
Publishing is restricted to `main`. The publishing jobs deploy through the `clawhub-publish`
|
|
313
320
|
environment, whose deployment branch policy rejects any other ref, so a manual dispatch from
|
|
314
321
|
a feature branch stops before it can upload. `CLAWHUB_TOKEN` is a repository secret, not an
|
|
315
|
-
environment secret:
|
|
316
|
-
|
|
322
|
+
environment secret: the skill call hands it to upstream, which reads it as `clawhub_token`, and
|
|
323
|
+
a job that calls a reusable workflow cannot declare an environment. Forwarding the value
|
|
317
324
|
through a job output does not help either — GitHub refuses to emit a secret-valued output and
|
|
318
325
|
logs `Skip output 'clawhub_token' since it may contain secret`.
|
|
319
326
|
|
package/package.json
CHANGED