Repository navigation
chore: require Node 26.13.0 for site tooling - #687
Merged
Merged
Conversation
Contributor
🤖 MERGED
GitHub merged this pull request. No material findings were recorded. 34734f68-705d-4259-9e53-84e17a8d4a8a |
Contributor
There was a problem hiding this comment.
Harlan Agent Kit posted this automated review. AI open source policy.
Automated Review: READY.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
❓ Type of change
📚 Description
Standardize site tooling on Node 26.13.0 to match the current LTS release. Local version files and workflow inputs now use the same pin.
Update the harness image to Node 26.13.0. Build that image in the existing hosted CI check.
This site requires Node 26.13.0 or newer within the 26.x release line.
📝 Migration
Install Node 26.13.0 locally, then run
pnpm install --frozen-lockfile.