From fe63907d608a7e1a64da1c9438b4d380439fcc02 Mon Sep 17 00:00:00 2001
From: fro-bot <80104189+fro-bot@users.noreply.github.com>
Date: Fri, 15 May 2026 21:46:46 +0000
Subject: [PATCH] fix(ci): constrain @types/node to LTS (even) majors and caret
 ranges in autoheal prompt

The daily autoheal schedule prompted a bump to @types/node 25, which is
an odd-numbered (non-LTS) version. The repository only uses even-numbered
Node.js LTS releases and pins dependencies with caret ranges, not bare
major version numbers.

Updated SCHEDULE_PROMPT to note these conventions so future autoheal
runs will skip odd major versions and use caret version ranges for
@types/node.
---
 .github/workflows/fro-bot.yaml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/.github/workflows/fro-bot.yaml b/.github/workflows/fro-bot.yaml
index c279ac3..37c3f8a 100644
--- a/.github/workflows/fro-bot.yaml
+++ b/.github/workflows/fro-bot.yaml
@@ -88,6 +88,9 @@ env:
          If the minimum required version has changed, open a PR updating the constraint.
        - Check for major version bumps in devDependencies (typescript, @biomejs/biome,
          @types/bun, @types/node, rimraf). Create one PR per major bump.
+         IMPORTANT: @types/node must only be bumped to even major versions (LTS
+         releases: 20, 22, 24, 26, …). Never bump to odd-numbered major versions.
+         Do not pin to a bare major number — use a caret range (e.g., ^24.x).
        - Pin any unpinned GitHub Actions in .github/workflows/ to full commit SHAs.
        Check changeset hygiene:
        - Verify no unreleased changeset entries have drifted out of sync with package.json version.