Conversation
The Dockerfile installed pnpm via 'npm install -g pnpm' which resolves to the latest tag. pnpm 11.1.2 (published 2026-05-14 11:44 UTC) tightened overrides validation, causing 'pnpm install --frozen-lockfile' to fail with ERR_PNPM_LOCKFILE_CONFIG_MISMATCH against the existing keeperhub-events/pnpm-lock.yaml (generated with pnpm 10). Pin to pnpm@10 to match the version used to author the lockfile and the pinning convention already used by the root, sandbox, and scheduler Dockerfiles.
…e-overrides hotfix: pin pnpm@10 in event-tracker Dockerfile
joelorzet
requested review from
a team,
OleksandrUA,
eskp and
suisuss
and removed request for
a team
The MCP route handlers and the /api/* routes they call (execute, workflow invocation, status, resources) run in the same Next.js process. They were being called through the public hostname (NEXT_PUBLIC_APP_URL, app.keeperhub.com), so each internal call exited the pod to the Cloudflare edge. Once CF's "Block AI Scrapers and Crawlers" managed challenge was enabled, those pod-to-edge requests started getting a managed challenge and 403ing tool execution (execute_contract_call, execute_transfer, etc.). getBaseUrl returning the public URL is correct for OAuth metadata documents the client must reach. The defect was reusing that same value for the server's own internal fetches. Adds getInternalApiBaseUrl() (in-pod loopback, INTERNAL_API_URL override) and routes createMcpServer / createWorkflowMcpServer through it. OAuth-metadata uses of getBaseUrl are unchanged. The threaded parameter is renamed baseUrl -> internalApiBaseUrl so it cannot be silently re-wired to the public URL again.
fix: route MCP server-to-server API calls over in-pod loopback
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
2 participants
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.
Summary
Promote the following merged PRs from staging to prod:
Post-deploy verification
deploy-keeperhubworkflow finishes greencurl -fsS https://app.keeperhub.com/api/healthreturns 200