Repository navigation
@tus/server: use Node 26 for private tooling - #896
Merged
Merged
Conversation
|
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.
Private build and release tooling should run on the validated Node 26 runtime while published packages retain Node 20.19 compatibility. Pin the build/lint and release jobs to exact Node 26.12.1 and align the contributor release-tooling instructions. Keep the existing Node 20 test job, package engine ranges, dependency lockfile, and release commands intact.
Validation: workflow YAML parsing and
git diff --checkpass. Council review completed; its request to float the runtime was declined because this upgrade explicitly pins the validated release, now documented beside the pins. Per repository instructions, actual Node 26 build/lint and the existing secret-backed Node 20 suite run in CI rather than locally. Publishing was not run.CI: Node 26 build/lint and existing Node 20 secret-backed tests pass. Socket checks pass. Devin Review passed with no issues found; its completed review and PR comments were read.
Reviewed commit:
3ace60ffca8639459b0a1b0bf22f1f079d8e4ae7.🤖 Claimed by kvz on
framework1/tus-node-serversince 2026-10-21 · resume:codex resume 01a15ee6-8ad4-7ec2-a0c6-c6d3ac36a367