chore(npm): prefix hyperdb-mcp repository URLs with git+#48
Merged
StefanSteiner merged 4 commits intoMay 27, 2026
Merged
Conversation
npm publish auto-corrected the repository.url field in all five hyperdb-mcp npm package.json files at publish time and emitted a warning recommending `npm pkg fix`. Apply the canonical form (git+https://...) directly so packed tarballs match what npm publishes and the warning goes away. hyperdb-api-node/package.json already used the git+ prefix; the per- platform hyperdb-api-node directories have no repository block.
The verify job was re-running the full test matrix on the tagged SHA (workspace tests + hyperdb-bootstrap tests + URL verify), adding ~20 minutes to every release. Since CI already ran on the merge commit that release-please tagged, all of that coverage was redundant. Replace the test re-run with a check-runs poll mirroring the pattern in npm-build-publish.yml's verify-ci job. Required checks: rustfmt, clippy, cargo-audit, cargo-deny, version consistency, publish dry-run, the 3-OS test matrix, and hyperdb-api-node (build + smoke). A maintainer running workflow_dispatch on a SHA that never had CI would have all checks evaluate to "no checks present" — guard with TOTAL > 0 so absent CI aborts publish rather than silently passing. Keep the verify-hyperd-pin step as a standalone safety check — it HEAD-requests each platform's pinned hyperd download URL right before publishing in case Tableau rotated something between merge time and tag time. Cheap (~1 min). Drops timeout-minutes from 60 to 35 to match npm-build-publish.yml's verify-ci.
Hyper does not support ON CONFLICT / INSERT ... ON DUPLICATE KEY. Add guidance to both the LLM-facing readme returned by get_readme and the general README.md showing the UPDATE + INSERT WHERE NOT EXISTS pattern. Note that Hyper does support transactions at the API level, but each MCP execute call runs one statement and auto-commits — the pattern is still race-safe because hyperd serializes statements on the same DB.
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.
npm publish auto-corrected the repository.url field in all five hyperdb-mcp npm package.json files at publish time and emitted a warning recommending
npm pkg fix. Apply the canonical form (git+https://...) directly so packed tarballs match what npm publishes and the warning goes away.hyperdb-api-node/package.json already used the git+ prefix; the per- platform hyperdb-api-node directories have no repository block.
fix(npm): prefixes repository.url with git+ in 5 hyperdb-mcp package.json files, dropping the npm warn publish "auto-corrected" warnings.
chore(ci): replaces release.yml's verify job (which re-ran the full test matrix, ~20 min) with a check-runs poll on the tagged SHA. Mirrors the pattern already in npm-build-publish.yml. Keeps verify-hyperd-pin as a cheap pre-publish safety check.
chore(doc): update breaking change version