@friggframework/core 2.0.0--canary.596.6355e72.0 → 2.0.0--canary.596.97a5c6b.0

package/handlers/routers/health.js

@@ -511,6 +511,10 @@ router.get('/health/ready', async (_req, res) => {
     });
 });
 
-const handler = createAppHandler('HTTP Event: Health', router);
+// shouldUseDatabase: false — health must NOT eagerly open a DB connection.
+// /health/live is a pure liveness probe (no DB), and /health/ready probes the
+// DB itself and degrades to 503 gracefully. Eager-connect at handler entry
+// would turn a DB outage into a 500 for both (killing healthy containers).
+const handler = createAppHandler('HTTP Event: Health', router, false);
 
 module.exports = { handler, router };

package/handlers/routers/integration-defined-routers.js

@@ -94,9 +94,23 @@ for (const IntegrationClass of integrationClasses) {
     };
 
     for (const [bindingName, group] of bindingGroups) {
+        // The function key is the wire contract with the devtools serverless
+        // generator (integration-builder.js builds the identical key). Keep
+        // the derivation here and there IN SYNC.
         const fnKey = `${IntegrationClass.Definition.name}__${sanitizeBindingKey(
             bindingName
         )}`;
+        // Two binding keys that sanitize to the same value (e.g. "hub-spot"
+        // and "hubspot") would silently overwrite each other's handler. The
+        // namespaced-path claim() above can't catch it (the paths differ), so
+        // fail loud here.
+        if (Object.prototype.hasOwnProperty.call(handlers, fnKey)) {
+            throw new Error(
+                `Integration "${IntegrationClass.Definition.name}" extension handler conflict: ` +
+                    `binding "${bindingName}" sanitizes to "${fnKey}", which is already taken. ` +
+                    `Use binding keys that are distinct after stripping non-alphanumeric characters.`
+            );
+        }
         handlers[fnKey] = {
             handler: createAppHandler(
                 `HTTP Event: ${IntegrationClass.Definition.name} extension ${bindingName}`,

package/integrations/EXTENSIONS.md

@@ -55,6 +55,8 @@ Each extension binding is mounted under its **binding key**, on its own dedicate
 
 So the full URL is `/api/{integration-name}-integration/{bindingKey}{route.path}`. Register that URL with the upstream provider (e.g. paste it into your HubSpot app's webhook settings). Hit it and the bound method (`onHubSpotEvent`) fires on the resolved per-account integration instance.
 
+> **⚠️ Breaking:** extension routes used to mount un-namespaced (`/api/{x}-integration/webhooks`). They are now namespaced under the binding key. Any provider webhook already registered against the old path must be re-pointed at the new `/{bindingKey}` URL — and for signature schemes that sign the full URL (e.g. HubSpot v3), the old registration will also fail verification until updated.
+
 ## `useDatabase` — does the receiver open a DB connection?
 
 Each extension declares whether its route handler should open a database connection:
@@ -72,6 +74,7 @@ module.exports = {
 - **Default is `false`** — a webhook receiver that only verifies a signature and enqueues should not pay for a DB connection (faster cold start; at build time its Lambda doesn't get the Prisma layer).
 - Set `useDatabase: true` at the **extension level** if the receiver itself needs the DB. A binding may override it locally (`extensions: { x: { extension, useDatabase: true } }`), though that's rarely needed.
 - Resolution order: `binding.useDatabase ?? extension.useDatabase ?? false`.
+- Scope note: `false` is the default **for extension routes**. `createHandler` itself still defaults `shouldUseDatabase: true` for the integration's own catch-all handler and the legacy `Definition.webhooks: true` path — those connect as before. The `false` default applies only to the per-binding extension handler.
 
 If `useDatabase` is `false`, the receiver must not touch the database. Work that needs the DB (e.g. resolving `portalId → integrationId`) belongs in the queue worker that processes the dispatched event, not in the receiver.
 

package/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@friggframework/core",
     "prettier": "@friggframework/prettier-config",
-    "version": "2.0.0--canary.596.6355e72.0",
+    "version": "2.0.0--canary.596.97a5c6b.0",
     "dependencies": {
         "@aws-sdk/client-apigatewaymanagementapi": "^3.588.0",
         "@aws-sdk/client-kms": "^3.588.0",
@@ -38,9 +38,9 @@
         }
     },
     "devDependencies": {
-        "@friggframework/eslint-config": "2.0.0--canary.596.6355e72.0",
-        "@friggframework/prettier-config": "2.0.0--canary.596.6355e72.0",
-        "@friggframework/test": "2.0.0--canary.596.6355e72.0",
+        "@friggframework/eslint-config": "2.0.0--canary.596.97a5c6b.0",
+        "@friggframework/prettier-config": "2.0.0--canary.596.97a5c6b.0",
+        "@friggframework/test": "2.0.0--canary.596.97a5c6b.0",
         "@prisma/client": "^6.17.0",
         "@types/lodash": "4.17.15",
         "@typescript-eslint/eslint-plugin": "^8.0.0",
@@ -80,5 +80,5 @@
     "publishConfig": {
         "access": "public"
     },
-    "gitHead": "6355e7230ef1f29f10e5336c88d4ddd257dffe18"
+    "gitHead": "97a5c6bc4217a0fcaaa6e6fa7baeb4b179f06d41"
 }