@nithin554/code-crawler 0.1.71 → 0.1.72

package/README.md

@@ -307,11 +307,11 @@ plugin is published there too:
 
 Publishing is restricted to `main`. Both jobs deploy through the `clawhub-publish`
 environment, whose deployment branch policy rejects any other ref, so a manual dispatch from
-a feature branch stops before it can upload. The `CLAWHUB_TOKEN` secret lives on that
-environment rather than on the repository, so a publish can only read it after the gate has
-accepted the ref; the environment-bound `guard` job is what passes it to the publish call,
-because a job that calls a reusable workflow cannot declare an environment and therefore
-cannot read an environment secret itself.
+a feature branch stops before it can upload. `CLAWHUB_TOKEN` is a repository secret, not an
+environment secret: an environment secret is only readable by a job that declares that
+environment, and a job that calls a reusable workflow cannot declare one. Forwarding the value
+through a job output does not help either — GitHub refuses to emit a secret-valued output and
+logs `Skip output 'clawhub_token' since it may contain secret`.
 
 ### One command
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nithin554/code-crawler",
-  "version": "0.1.71",
+  "version": "0.1.72",
   "mcpName": "io.github.nithin554/code-crawler",
   "description": "Static and dynamic call tracing MCP server backed by a SQLite property graph of your codebase",
   "type": "module",