Gather rawRelease for future replays. Improve prompts

prisma/migrations/20250115142547_add_raw_release/migration.sql

@@ -0,0 +1,14 @@
+-- CreateTable
+CREATE TABLE "RawRelease" (
+    "id" TEXT NOT NULL,
+    "body" JSONB NOT NULL,
+    "releaseId" TEXT NOT NULL,
+
+    CONSTRAINT "RawRelease_pkey" PRIMARY KEY ("id")
+);
+
+-- CreateIndex
+CREATE UNIQUE INDEX "RawRelease_releaseId_key" ON "RawRelease"("releaseId");
+
+-- AddForeignKey
+ALTER TABLE "RawRelease" ADD CONSTRAINT "RawRelease_releaseId_fkey" FOREIGN KEY ("releaseId") REFERENCES "Release"("id") ON DELETE CASCADE ON UPDATE CASCADE;

prisma/migrations/migration_lock.toml

@@ -1,3 +1,3 @@
 # Please do not edit this file manually
-# It should be added in your version-control system (i.e. Git)
+# It should be added in your version-control system (e.g., Git)
 provider = "postgresql"

prisma/schema.prisma

@@ -24,7 +24,7 @@ model Alert {
 }
 
 model Release {
-  id          String   @id @default(cuid())
+  id          String      @id @default(cuid())
   name        String
   org         String
   repo        String
@@ -35,6 +35,7 @@ model Release {
   publishedAt DateTime
   authors     String[]
   summary     String
+  rawRelease  RawRelease?
 }
 
 enum Source {
@@ -54,3 +55,11 @@ model AlertContext {
 
   alert Alert @relation(fields: [alertId], references: [id], onDelete: Cascade)
 }
+
+model RawRelease {
+  id        String @id @default(cuid())
+  body      Json
+  releaseId String @unique
+
+  release Release @relation(fields: [releaseId], references: [id], onDelete: Cascade)
+}

src/aggregator/chains.ts

@@ -78,11 +78,12 @@ ${stringify(
 	{ indent: 2 }
 ).slice(0, 200000)}
 
-Check-results amd checkly configuration details are already provided in the UI. Focus on the root cause analyisis and potential mitigations. Help the user to resolve the issue.
+Check-results amd checkly configuration details are already provided in the UI. Focus on the root cause analysis and potential mitigations. Help the user to resolve the issue.
 Generate a condensed summary of your root cause analysis of the current situation. 
 Focus on the essentials, provide a concise overview and actionable insights. 
 Provide reasoning and the source of the information. Max. 100 words. Include links to relevant context if applicable.
 Be concise, insightful and actionable, skip the fluff, no yapping.
+If a recent release is the most likely root cause, provide a link to the release diff. 
 
 *Summary:* `,
 		maxTokens: 500,

src/routes/githubwebhook.ts

@@ -1,4 +1,4 @@
-import {PrismaClient} from '@prisma/client';
+import {Prisma, PrismaClient} from '@prisma/client';
 
 import crypto, {sign} from "crypto";
 import timers from "node:timers/promises";
@@ -96,7 +96,7 @@ router.post(
           releaseEvent.repository.owner.login
         );
 
-        const previousRelease = await withRetry(() =>github.getPreviousReleaseTag(
+        const previousRelease = await withRetry(() => github.getPreviousReleaseTag(
           releaseEvent.repository.owner.login,
           releaseEvent.repository.name,
           releaseEvent.release.tag_name
@@ -126,7 +126,7 @@ router.post(
         }).blocks;
 
         console.log('Creating a new release in the database');
-        await prisma.release.create({
+        const createdRelease = await prisma.release.create({
           data: {
             name: releaseName,
             releaseUrl: releaseEvent.release.html_url,
@@ -140,6 +140,13 @@ router.post(
             summary: release.summary,
           }
         });
+        await prisma.rawRelease.create({
+          data: {
+            body: releaseEvent as unknown as Prisma.InputJsonValue,
+            releaseId: createdRelease.id,
+          },
+        });
+
         console.log('Posting a message to Slack');
         await app.client.chat.postMessage({
           channel: process.env.SLACK_RELEASE_CHANNEL_ID as string,