@nithin554/code-crawler 0.1.74 → 0.1.75

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 +5 -1
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -303,7 +303,11 @@ plugin is published there too:
303
303
  of copying the npm version; a release whose skill publish fails leaves the two numbers one
304
304
  apart until the next publish.
305
305
  - **Plugin** — published as the `code-crawler` bundle plugin, versioned from the release tag:
306
- release `v0.1.67` publishes the bundle at `0.1.67`.
306
+ release `v0.1.67` publishes the bundle at `0.1.67`. The bundle's own
307
+ `plugins/code-crawler/package.json` is packaging metadata — ClawHub needs a package
308
+ manifest to inspect the bundle and build its ClawPack artifact, and warns when one is
309
+ missing — so the release workflow stamps the tag's version into it, packs the bundle, and
310
+ hands that tarball to the publish; the committed `version` is only a placeholder.
307
311
 
308
312
  Publishing is restricted to `main`. Both jobs deploy through the `clawhub-publish`
309
313
  environment, whose deployment branch policy rejects any other ref, so a manual dispatch from
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nithin554/code-crawler",
3
- "version": "0.1.74",
3
+ "version": "0.1.75",
4
4
  "mcpName": "io.github.nithin554/code-crawler",
5
5
  "description": "Static and dynamic call tracing MCP server backed by a SQLite property graph of your codebase",
6
6
  "type": "module",