fix(distribution): pin exact npm package launchers - #26
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🧠 Hunch — Engineering Memory Guard✅ This PR touches no recorded invariants (directly or via blast radius) and re-introduces nothing deliberately retired across 15 changed file(s). 📜 Hunch Constitution — 2 policy receipt(s)
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
@davesheffer/hunch@<version>package spec frompackage.jsonnpxcannot fall through to a stale global binaryWhy
Hunch 1.8.4 was consumed through a GitHub release tarball. Hunch 1.9.3 is published through the npm registry with OIDC provenance, and the old GitHub tarball URL no longer exists. Merely replacing the version in the old URL shape would break MCP, hooks, and CI.
Inside a Hunch source checkout, a direct exact-package
npxcommand could also treat the local package name as satisfying the request and execute an older globalhunch. The distinct npm alias forces resolution of the exact published package.Impact
Committed MCP/provider configuration, generated lifecycle hooks, and Hunch Guard workflows now execute the same deterministic package version that generated them. A future release bump updates the shared version source and the regression tests force all distribution surfaces to advance together.
Validation
npm run typechecknpm run buildnpx tsx --test test/version.test.ts test/providers.test.ts test/antigravity.test.ts test/ci-action.test.ts(20 passed)npx -y --package=hunch-exact@npm:@davesheffer/hunch@1.9.3 hunch --version→1.9.3