@sentry/junior-sentry 0.261.0 → 0.263.0

package/README.md

@@ -50,7 +50,7 @@ For metric alerts, also enable **Alert Rule Action** on the integration and add
 Junior verifies `Sentry-Hook-Signature`, rejects payloads outside `SENTRY_WEBHOOK_ORG`, and publishes:
 
 - `issue.created` for `org/project#issueId` and `org/project`.
-- `metric_alert.critical`, `metric_alert.warning`, and `metric_alert.resolved` for `metric-alert:org/alertRuleId`.
+- `metric_alert.critical`, `metric_alert.warning`, and `metric_alert.resolved` for `metric-alert:org/alertRuleId` and for `org/project` of each project on the alert rule.
 
 Create watches/event automations before the webhook arrives; unmatched deliveries are not replayed.
 

package/dist/{chunk-6VG4NPNH.js → chunk-KUDJGV46.js}

@@ -66,7 +66,10 @@ var metricAlertWebhookSchema = z.object({
     description_text: z.string().optional(),
     description_title: z.string().optional(),
     metric_alert: z.object({
-      alert_rule: z.object({ id: z.coerce.string().min(1) }).passthrough(),
+      alert_rule: z.object({
+        id: z.coerce.string().min(1),
+        projects: z.array(z.string().min(1)).optional()
+      }).passthrough(),
       id: z.coerce.string().min(1)
     }).passthrough(),
     web_url: z.string().url()
@@ -161,17 +164,22 @@ function normalizeMetricAlertEvents(input) {
     data.description_text,
     `URL: ${data.web_url}`
   ].filter((part) => Boolean(part)).join("\n");
+  const event = {
+    // One event per incident state. Sentry retries get new Request-IDs.
+    eventKey: `sentry:${resource.identifier}:${incidentId}:${eventType}`,
+    eventType,
+    occurredAtMs: providerTime(input.hookTimestamp) ?? Date.now(),
+    trustedSummary: `${resource.label} is ${parsed.data.action}.`,
+    data: { alertRuleId, incidentId, url: data.web_url },
+    untrustedText
+  };
+  const projects = [...new Set(data.metric_alert.alert_rule.projects ?? [])];
   return [
-    {
-      // One event per incident state. Sentry retries get new Request-IDs.
-      eventKey: `sentry:${resource.identifier}:${incidentId}:${eventType}`,
-      eventType,
-      identifier: resource.identifier,
-      occurredAtMs: providerTime(input.hookTimestamp) ?? Date.now(),
-      trustedSummary: `${resource.label} is ${parsed.data.action}.`,
-      data: { alertRuleId, incidentId, url: data.web_url },
-      untrustedText
-    }
+    { ...event, identifier: resource.identifier },
+    ...projects.map((project) => ({
+      ...event,
+      identifier: sentryProjectResource({ org, project }).identifier
+    }))
   ];
 }
 function normalizeSentryEvents(input) {

package/dist/index.js

@@ -6,7 +6,7 @@ import {
   createSentryWebhookRoute,
   sentryWebhookOrg,
   sentryWebhookSecret
-} from "./chunk-6VG4NPNH.js";
+} from "./chunk-KUDJGV46.js";
 
 // src/index.ts
 import {
@@ -106,8 +106,14 @@ function sentryPlugin() {
         },
         {
           type: "project",
-          supportedEvents: [...SENTRY_ISSUE_EVENTS],
-          suggestedEvents: [...SENTRY_ISSUE_EVENTS]
+          supportedEvents: [
+            ...SENTRY_ISSUE_EVENTS,
+            ...SENTRY_METRIC_ALERT_EVENTS
+          ],
+          suggestedEvents: [
+            ...SENTRY_ISSUE_EVENTS,
+            ...SENTRY_METRIC_ALERT_SUGGESTED_EVENTS
+          ]
         },
         {
           type: "metric_alert",

package/dist/testing.js

@@ -5,7 +5,7 @@ import {
   sentryProjectResource,
   sentryWebhookOrg,
   sentryWebhookSecret
-} from "./chunk-6VG4NPNH.js";
+} from "./chunk-KUDJGV46.js";
 export {
   createSentryWebhookRoute,
   normalizeSentryEvents,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sentry/junior-sentry",
-  "version": "0.261.0",
+  "version": "0.263.0",
   "private": false,
   "publishConfig": {
     "access": "public"
@@ -27,7 +27,7 @@
   ],
   "dependencies": {
     "zod": "^4.5.4",
-    "@sentry/junior-plugin-api": "0.261.0"
+    "@sentry/junior-plugin-api": "0.263.0"
   },
   "devDependencies": {
     "@oxlint/plugins": "1.79.0",

package/skills/sentry/SKILL.md

@@ -27,6 +27,7 @@ Before declaring a Sentry data surface unavailable, verify the current CLI help:
 2. Execute via CLI:
 
 - Use `sentry <command>` for structured queries.
+- A repo can put its own `sentry` program first on PATH, for example in a `getsentry/sentry` checkout. If `sentry --help` does not show the Sentry CLI, run `/vercel/sandbox/.junior/bin/sentry` instead.
 - The runtime authenticates Sentry HTTP traffic for this skill. Do not set or print token env vars.
 - Read [references/cli-commands.md](references/cli-commands.md) when choosing command shapes, target formats, flags, API fallback, or troubleshooting behavior.
 - Read [references/sandbox-runtime.md](references/sandbox-runtime.md) before relying on sandbox credentials.