Skip to content

fix(ci): constrain @types/node to LTS (even) majors and caret ranges in autoheal prompt #134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fro-bot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(ci): constrain @types/node to LTS (even) majors and caret ranges in autoheal prompt #134

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .github/workflows/fro-bot.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down