v1.6.3

[rahlk]

A single-fix patch release. No breaking changes — nothing to migrate, and the Neo4j schema contract is unchanged at 2.0.0.

The application node carries its name again

Analysis output identifies the application by its canonical id (can://<app>), but the human-readable name had no field of its own, so consumers had to parse it back out of the id string. This release restores it as a first-class field on the application root node, in both projections:

• analysis.json — application.name
• Neo4j — a name property on the :Application / :TSApplication node

The value is your normalized --app-name, or the input directory's basename when you don't pass one.

{
  "id": "can://<app>", "name": "<app>", "kind": "application", ...
}

This is additive: name sits alongside id, which is unchanged, so existing queries, ids, and downstream consumers keep working untouched. On the Neo4j side, name joins the :Application property set without moving the contract version.

Upgrade

PyPI:

pip install -U "codeanalyzer-typescript==1.6.3"

Homebrew:

brew upgrade codellm-devkit/homebrew-tap/codeanalyzer-typescript

Shell installer (prebuilt binary; macOS and Linux):

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/codellm-devkit/codeanalyzer-typescript/releases/latest/download/cants-installer.sh | sh

Links

• GitHub release v1.6.3
• Full diff since v1.6.2
• #213 — fix(schema): restore application name alongside canonical id

What's Changed

• fix(schema): Restore TypeScript application name by @rohanarora in fix(schema): Restore TypeScript application name #213
• chore(release): 1.6.3 by @rahlk in chore(release): 1.6.3 #214

New Contributors

• @rohanarora made their first contribution in fix(schema): Restore TypeScript application name #213

Full Changelog: v1.6.2...v1.6.3

---

This discussion was created from the release v1.6.3.