Repository navigation
v0.145.0
MCP: PrismaMcpOAuthStore and PrismaNonceStore, shared stores on the app's database
New, nothing to migrate. See MCP Server → The store and Approval.
PrismaMcpOAuthStore(gemi/services): a ready-madeMcpOAuthStoreon three models (McpOAuthClient,McpOAuthCredential,McpOAuthUse; the schema is in the docs), given as gemi ORM model classes or a Prisma client's delegates. It addsconnectedApps(userId),disconnect(userId, familyId),revokeUser(userId),prune()andnonces().PrismaNonceStore(gemi/ai): aNonceStoreon akey/expiresAtmodel, forroute.mcp.remote.nonces(or anAgentController'snonces) on an app without Redis. A nonce is spent by inserting it as the primary key, so it is single-use across instances.prune()deletes expired rows.- An app that wrote its own Prisma store with these models (like the one in the docs before) can switch to
PrismaMcpOAuthStorewithout a migration, as long asMcpOAuthCredentialhascreatedAt DateTime @default(now()).
MCP: route.mcp.remote.onCall, an audit hook for remote tool calls
New, nothing to migrate. See MCP Server → Auditing calls.
onCall(event)runs once after every remotetools/callhas been answered, including failures and refusals. The event carries the user, the resolver (via), the credential id (the OAuth grant or API key id), the OAuthclientId, the scopes, the tool, its arguments, theoutcome(ok,errorordenied, with areasonfordenied), whether the user approved it, anddurationMs.- It is awaited before the answer is sent. A hook that throws is logged and does not change the answer.
- New exported types:
McpCallEvent,McpCallOutcome,McpCallDenial(fromgemi/services).
Meta.openGraph without an image, and twitter:card (#961)
New, plus a small behaviour change. Nothing to migrate. See Views & Layouts.
imageis optional.og:imageis rendered only when it is set.twitter:cardis always rendered whenMeta.openGraphis called:summary_large_imagewhentwitterImage ?? imageis set (as before),summaryotherwise. Before, a page withouttwitterImagegot notwitter:card. The newtwitterCardoption picks the card type explicitly.- Image paths.
imageandtwitterImagenow get the app origin each on their own. Before, a relativeimageprefixedtwitterImagetoo, even an absolute one, and a relativetwitterImagenext to an absoluteimagewas left relative. Pages that pass onlyimagerender exactly as before.
A trusted client-IP header without route.domains, and ip:port in X-Forwarded-For (#958)
New, plus a small behaviour change. Nothing to migrate. See Configuration → A trusted client-IP header.
GEMI_CLIENT_IP_HEADER,GEMI_PROXY_SECRET_HEADER,GEMI_PROXY_SECRET(new). These do whatroute.domains.trustProxy.clientIpHeaderdoes, for an app withoutroute.domains. On a request whose secret header matches, the client-IP header's first entry becomes the only entry ofX-Forwarded-For, before the global middleware, soclientIp(req)and every rate limit see it. Without the secret, the addressGEMI_TRUST_PROXYchose is kept. Set all three or none: a partial set, a bad header name or a secret under 16 characters fails the boot. Behind Azure Front Door:GEMI_CLIENT_IP_HEADER=x-azure-clientip,GEMI_PROXY_SECRET_HEADER=x-azure-fdid,GEMI_PROXY_SECRET=<Front Door profile ID>.ip:portentries (behaviour change). TheX-Forwarded-ForentryGEMI_TRUST_PROXY=<n>picks is now stored without its port (203.0.113.7:51234gives203.0.113.7,[2001:db8::1]:443gives2001:db8::1). Before, each connection's source port gave the client a fresh rate-limit bucket. A chosen entry that is not an IP address at all now falls back to the socket's peer address instead of being used as sent.clientIp(req)and the broadcast per-IP cap drop the port as well.route.domains.trustProxy.clientIpHeadernow accepts a value with a port and reads it without the port. Before, such a value was ignored.