From c972102726b6c635ee2c4030134aed040f929c98 Mon Sep 17 00:00:00 2001 From: Colby Mchenry Date: Tue, 26 May 2026 03:31:05 -0500 Subject: [PATCH] chore: sync package-lock.json to 0.9.5 (#440) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The 0.9.5 release bumped package.json but not package-lock.json — the EUSAGE-on-npm-ci drift that #439's auto-sync workflow step now prevents going forward. Fixing main retroactively so contributors and any non-Release CI path see a consistent state. Impact: zero on the published 0.9.5 release. The npm tarball ships only npm-shim.js + package.json + README.md (no lock file), so end-user installs are unaffected. The GitHub Release archives are platform- bundled-Node tars from build-bundle.sh — also no lock file. Only fresh git clones of main running 'npm ci' would have hit EUSAGE; this commit fixes that. Two-line diff: package-lock.json's top-level `version` and `packages[''].version` both 0.9.4 → 0.9.5. No dependency changes. Co-authored-by: Claude Opus 4.7 (1M context) --- package-lock.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/package-lock.json b/package-lock.json index f186ddc..c79704f 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "@colbymchenry/codegraph", - "version": "0.9.4", + "version": "0.9.5", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "@colbymchenry/codegraph", - "version": "0.9.4", + "version": "0.9.5", "license": "MIT", "dependencies": { "@clack/prompts": "^1.3.0",