Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion .node-version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
26.5.0
26.5.1
1 change: 1 addition & 0 deletions changelog.d/0000-node-version-26.5.1.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Bump the pinned dev/CI Node to 26.5.1 (latest stable), aligning `.node-version` with the compat-matrix oracle in `external-tools.json`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win

Use the actual PR number in the changelog filename.

Rename this file to changelog.d/<PR>-node-version-26.5.1.md; 0000 does not satisfy the required PR-keyed fragment convention. As per coding guidelines, changelog fragments must use changelog.d/<PR>-<slug>.md without a version header.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@changelog.d/0000-node-version-26.5.1.md` at line 1, Rename the changelog
fragment from the 0000-prefixed filename to
changelog.d/<actual-PR-number>-node-version-26.5.1.md, preserving its existing
content and omitting any version header.

Source: Coding guidelines

Loading