fix: handle skipped benchmark cases in create-release.ts

- Added logic to format release descriptions when benchmark results are missing, providing clear messaging about the absence of data.
- Updated release name generation to reflect when benchmarks are skipped, ensuring accurate representation in release notes.
- This change improves the clarity and usability of release information in scenarios where no performance data is available.

Author: ImBIOS

scripts/create-release.ts

@@ -53,6 +53,30 @@ function formatReleaseDescription(
     day: 'numeric',
   });
 
+  // Handle case when benchmark was skipped (empty results)
+  if (!results || !results.tools) {
+    return `# 📊 Monorepo Tools Benchmark Results - ${date}
+
+## ⚠️ No Benchmark Data Available
+
+The benchmark was skipped in this run. No performance data is available.
+
+## Tool Versions
+
+| Tool | Version |
+|------|---------|
+| Nx | ${versions.nx} |
+| Turbo | ${versions.turbo} |
+| Lerna | ${versions.lerna} |
+| Lage | ${versions.lage} |
+| Node.js | ${versions.node} |
+| PNPM | ${versions.pnpm} |
+
+---
+
+*This release was automatically generated by the daily benchmark workflow. The benchmark was skipped for this run.*`;
+  }
+
   return `# 📊 Monorepo Tools Benchmark Results - ${date}
 
 ## Performance Results
@@ -107,9 +131,15 @@ function generateReleaseInfo(results: BenchmarkResults): ReleaseInfo {
     day: 'numeric',
   });
 
+  // Handle case when benchmark was skipped
+  const releaseName =
+    !results || !results.tools
+      ? `📊 Benchmark Results - ${date} (No Data - Benchmark Skipped)`
+      : `🚀 Benchmark Results - ${date} (Nx ${versions.nx}, Turbo ${versions.turbo})`;
+
   return {
     tagName,
-    releaseName: `🚀 Benchmark Results - ${date} (Nx ${versions.nx}, Turbo ${versions.turbo})`,
+    releaseName,
     description: formatReleaseDescription(results, versions),
   };
 }