Skip to content

feat(install): install and upgrade from GitHub Releases without npm - #327

Merged
ardelperal merged 1 commit into
mainfrom
feat/issue-326-install-without-npm
Sep 19, 2026
Merged

ardelperal merged 1 commit into
mainfrom
feat/issue-326-install-without-npm

Conversation

@ardelperal

Copy link
Copy Markdown
Owner

Closes #326

What changes

  • Bundle launchers: scripts/build-bundle.sh adds bin/codegraph-vba (POSIX) and bin/codegraph-vba.cmd (Windows) next to codegraph. install.sh links both and --uninstall removes both. install.ps1 needs no change because it puts the whole bin dir on PATH. Agent MCP configs and Dysflow launch codegraph-vba, which until now only the npm package provided.
  • codegraph-vba install: installs the CLI with the GitHub installer (install.ps1 / install.sh) instead of npm install -g. On failure it prints the exact command to run by hand.
  • Release workflow: the npm steps run only when NPM_TOKEN is set, and continue-on-error keeps an npm failure from failing a release whose GitHub Release already shipped.
  • Hints: the CLI load-failure message and the npm-upgrade failure path point at the GitHub installer (cliInstallCommand, a single source for the command).
  • README / CHANGELOG: the GitHub installer is the primary path; npm is marked legacy.

Not changed

  • The npm packaging itself (pack-npm.sh, shim, SDK entry). It still publishes while the token works.
  • codegraph-vba upgrade for bundle installs, which already used GitHub Releases only.

Verification

  • npm run build passes.
  • Local (Windows): upgrade.test.ts, installer-targets.test.ts and external-integration-doc.test.ts pass.
  • bundle-launchers.test.ts / install-sh-prune.test.ts are POSIX-only and run in CI. I also ran the same marker blocks by hand in Git Bash: both launchers are created, codegraph-vba.cmd matches codegraph.cmd byte for byte, both links are created, and an older bundle leaves no dangling link.
  • release.yml parses as YAML. The no-token path will only be exercised by a real release.
  • Not run: the Windows installer command end to end. It changes the user PATH, and v2.0.0 assets don't contain codegraph-vba.cmd until the next release.

🤖 Generated with Claude Code

- Bundles ship a codegraph-vba launcher next to codegraph, and install.sh
  links both, so agent MCP configs and Dysflow resolve it without npm.
- codegraph-vba install runs the GitHub installer script instead of npm.
- The release workflow publishes to npm only when NPM_TOKEN is set, and an
  npm failure no longer fails the release.
- README and CLI hints lead with the GitHub installer.

Closes #326
@ardelperal
ardelperal merged commit 426c0c0 into main Sep 19, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Install and upgrade from GitHub Releases without npm

1 participant