@pylonsync/webhooks 0.3.118 → 0.3.119

package/package.json

@@ -3,7 +3,7 @@
   "publishConfig": {
     "access": "public"
   },
-  "version": "0.3.118",
+  "version": "0.3.119",
   "type": "module",
   "main": "src/index.ts",
   "types": "src/index.ts",
@@ -12,8 +12,8 @@
     "check": "tsc -p tsconfig.json --noEmit"
   },
   "dependencies": {
-    "@pylonsync/sdk": "0.3.118",
-    "@pylonsync/functions": "0.3.118"
+    "@pylonsync/sdk": "0.3.119",
+    "@pylonsync/functions": "0.3.119"
   },
   "peerDependencies": {
     "bun-types": "*"

package/src/dispatch.ts

@@ -48,6 +48,26 @@ export async function dispatch(
 		}>
 	>("_pylonWebhookListEndpoints", { applicationId });
 
+	// `_pylonWebhookDeliver` is internal:true. Pylon framework's
+	// scheduler refuses public-action → internal-target enqueues to
+	// stop public actions becoming a router-bypass into internal
+	// helpers. Dispatch is by design called from public app actions
+	// (when an HTTP-triggered mutation wants to emit an event), so
+	// we need to grant the call admin authority before scheduling.
+	//
+	// On framework v0.3.118+ ctx.auth.elevate() exists; on older
+	// runtimes it doesn't. Guard the call so apps pinned to old
+	// pylon versions still type-check + run (they'd just get the
+	// SCHEDULE_FAILED error at the runAfter call, which is what they
+	// got before this fix landed — net no regression).
+	if (typeof ctx.auth.elevate === "function") {
+		await ctx.auth.elevate({
+			admin: true,
+			reason:
+				"webhooks plugin: scheduling _pylonWebhookDeliver (internal:true) — caller authority is the app's own dispatch trust boundary, the worker validates endpoint+tenant",
+		});
+	}
+
 	let scheduled = 0;
 	for (const ep of endpoints) {
 		if (ep.disabled) continue;

package/src/types.ts

@@ -74,7 +74,19 @@ export interface WebhookConfig {
 
 export interface WebhookCtx {
 	env: Record<string, string | undefined>;
-	auth: { userId?: string | null; tenantId?: string | null };
+	auth: {
+		userId?: string | null;
+		tenantId?: string | null;
+		/**
+		 * Optional — only present on Pylon framework v0.3.118+. The
+		 * dispatch path uses it (when available) to elevate the
+		 * caller to admin before scheduling the internal:true
+		 * `_pylonWebhookDeliver` worker. Without elevation the
+		 * scheduler's public-to-internal gate refuses the enqueue
+		 * and no webhooks deliver — see dispatch.ts comment.
+		 */
+		elevate?: (options: { admin: boolean; reason: string }) => Promise<void>;
+	};
 	runQuery: <T>(name: string, args: Record<string, unknown>) => Promise<T>;
 	runMutation: <T = unknown>(
 		name: string,