@checkstack/notification-teams-backend 0.0.30 → 0.0.31

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # @checkstack/notification-teams-backend
 
+## 0.0.31
+
+### Patch Changes
+
+- 32d52c6: Bulk notifications affecting multiple systems and collapse lifecycle events into a single card.
+
+  Notifications now carry an optional `subjects` array (the entities they affect) and an optional `collapseKey` (so related notifications collapse into one row per recipient). Incidents, maintenances, anomalies, healthchecks, and dependency-impact events route through these new fields, so an incident affecting three systems produces one in-app notification + one external send per subscriber instead of three. Lifecycle updates for the same entity (created → updated → resolved) also collapse, with an expandable "+N updates" timeline.
+
+  Subject kinds are namespaced as `<pluginId>.<localKind>` and built via type-safe helpers exported from each domain's common package (`createSystemSubject`, `incidentCollapseKey`, etc.). The frontend kind registry (`registerSubjectKind`) lets plugins bind icon + label for their kinds; unknown kinds fall back to a generic chip.
+
+  All notification strategies (SMTP, Slack, Discord, Teams, Telegram, Pushover, Gotify, Webex, Backstage) render the affected subjects natively in their format (HTML cards, Slack blocks, Discord embed fields, adaptive cards, markdown lists, etc.).
+
+- Updated dependencies [32d52c6]
+- Updated dependencies [32d52c6]
+- Updated dependencies [32d52c6]
+- Updated dependencies [32d52c6]
+  - @checkstack/notification-backend@1.0.0
+  - @checkstack/backend-api@0.14.0
+
 ## 0.0.30
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@checkstack/notification-teams-backend",
-  "version": "0.0.30",
+  "version": "0.0.31",
   "type": "module",
   "main": "src/index.ts",
   "checkstack": {
@@ -15,9 +15,9 @@
     "lint": "eslint src --ext .ts"
   },
   "dependencies": {
-    "@checkstack/backend-api": "0.13.0",
+    "@checkstack/backend-api": "0.13.1",
     "@checkstack/common": "0.7.0",
-    "@checkstack/notification-backend": "0.2.0",
+    "@checkstack/notification-backend": "0.2.1",
     "zod": "^4.2.1"
   },
   "devDependencies": {

package/src/index.ts

@@ -6,6 +6,7 @@ import {
   type NotificationStrategy,
   type NotificationSendContext,
   type NotificationDeliveryResult,
+  type NotificationSubject,
   type StrategyOAuthConfig,
 } from "@checkstack/backend-api";
 import { notificationStrategyExtensionPoint } from "@checkstack/notification-backend";
@@ -97,10 +98,18 @@ interface AdaptiveCardOptions {
   body?: string;
   importance: "info" | "warning" | "critical";
   action?: { label: string; url: string };
+  subjects?: NotificationSubject[];
 }
 
+const SUBJECT_STATUS_EMOJI = {
+  healthy: "🟢",
+  degraded: "🟡",
+  unhealthy: "🔴",
+  unknown: "⚪",
+} as const;
+
 function buildAdaptiveCard(options: AdaptiveCardOptions): object {
-  const { title, body, importance, action } = options;
+  const { title, body, importance, action, subjects } = options;
 
   const importanceColors: Record<string, string> = {
     info: "accent",
@@ -133,6 +142,32 @@ function buildAdaptiveCard(options: AdaptiveCardOptions): object {
     });
   }
 
+  if (subjects && subjects.length > 0) {
+    // Affected entities rendered as a FactSet — names link to URLs when
+    // present; status maps to a colored circle.
+    bodyElements.push(
+      {
+        type: "TextBlock",
+        text: "**Affected**",
+        weight: "bolder",
+        spacing: "medium",
+        wrap: true,
+      },
+      {
+        type: "FactSet",
+        facts: subjects.map((subject) => {
+          const prefix = subject.status
+            ? `${SUBJECT_STATUS_EMOJI[subject.status]} `
+            : "";
+          return {
+            title: prefix + subject.name,
+            value: subject.url ? `[Open](${subject.url})` : "—",
+          };
+        }),
+      },
+    );
+  }
+
   const card: Record<string, unknown> = {
     type: "AdaptiveCard",
     $schema: "http://adaptivecards.io/schemas/adaptive-card.json",
@@ -299,6 +334,7 @@ const teamsStrategy: NotificationStrategy<TeamsConfig> = {
         body: notification.body,
         importance: notification.importance,
         action: notification.action,
+        subjects: notification.subjects,
       });
 
       // Step 3: Send message to the chat