Summary
The CLI repo has dependency/tooling drift, including a patch drift on @insforge/shared-schemas versus the current shared schemas package used elsewhere in InsForge cleanup work.
This should be refreshed deliberately so the CLI stays aligned with the platform contracts and current toolchain.
Validation
Valid. npm --cache /private/tmp/insforge-cli-npm-cache outdated --json reported package drift on main@8f913e120e3d6cffecc435a4c9b8a7aebaec45be.
Observed drift:
@insforge/shared-schemas: current 1.1.52, wanted/latest 1.1.53
posthog-node: current 5.28.9, wanted/latest 5.35.6
eslint: current 10.0.2, wanted/latest 10.4.0
typescript-eslint: current 8.56.1, wanted/latest 8.60.0
vitest: current 4.1.0, wanted/latest 4.1.7
@types/node: current 22.19.13, wanted 22.19.19, latest 25.9.1
- Major latest versions also exist for
@clack/prompts, archiver, commander, open, and typescript.
Relevant Code
package.json:35 through package.json:44 - runtime dependencies.
package.json:46 through package.json:54 - dev dependencies.
Proposed Solution
Refresh safe patch/minor updates first, especially @insforge/shared-schemas, then evaluate major upgrades separately:
- Update lockfile and package ranges as appropriate.
- Run CLI unit tests, build, and any affected integration checks.
- For major upgrades, create follow-up issues/PRs if they need behavior changes.
Acceptance Criteria
- Safe patch/minor drift is updated or explicitly deferred with rationale.
@insforge/shared-schemas is aligned with the current platform schema package version.
npm run test, npm run lint, and npm run build pass after the update.
Summary
The CLI repo has dependency/tooling drift, including a patch drift on
@insforge/shared-schemasversus the current shared schemas package used elsewhere in InsForge cleanup work.This should be refreshed deliberately so the CLI stays aligned with the platform contracts and current toolchain.
Validation
Valid.
npm --cache /private/tmp/insforge-cli-npm-cache outdated --jsonreported package drift onmain@8f913e120e3d6cffecc435a4c9b8a7aebaec45be.Observed drift:
@insforge/shared-schemas: current1.1.52, wanted/latest1.1.53posthog-node: current5.28.9, wanted/latest5.35.6eslint: current10.0.2, wanted/latest10.4.0typescript-eslint: current8.56.1, wanted/latest8.60.0vitest: current4.1.0, wanted/latest4.1.7@types/node: current22.19.13, wanted22.19.19, latest25.9.1@clack/prompts,archiver,commander,open, andtypescript.Relevant Code
package.json:35throughpackage.json:44- runtime dependencies.package.json:46throughpackage.json:54- dev dependencies.Proposed Solution
Refresh safe patch/minor updates first, especially
@insforge/shared-schemas, then evaluate major upgrades separately:Acceptance Criteria
@insforge/shared-schemasis aligned with the current platform schema package version.npm run test,npm run lint, andnpm run buildpass after the update.