Repository navigation
@tus/server: update development Node typings with a named context return type - #868
Merged
Merged
Conversation
dependabot
Bot
added
dependencies
🦋 Changeset detectedLatest commit: 5758f24 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 22.13.7 to 26.2.0. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 26.1.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/types/node-26.1.2
branch
from
August 14, 2026 08:13
84e1b1f to
af9e66d
Compare
* origin/main: @tus/s3-store: clean up temp part files on upload failure (#885) @tus/server: revert Redis lockers to unblock releases Add FUNDING.yml pointing to the tus Open Collective (#883) feat(server): implement RedisLocker and IoRedisLocker (#846) [ci] release (#878) @tus/s3-store: avoid false completion on generic 404 (#877) [ci] release (#874) @tus/server: set CORS headers before early returns (#873)
Name the protected return type with the existing CancellationContext contract. Preserve current main brace-expansion lock entries when merging the dependency branch.
Compile packed declarations with TypeScript 5.8.2 and Node 20 and 22 typings without skipLibCheck. Exercise packaged cancellation and HTTP uploads on supported Node runtimes.
Use one locked external dependency installation for both packed revisions, retain strict diagnostics and runtime evidence, and add a patch changeset for the existing context return annotation.
Murderlon
changed the title
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.
Update development Node typings to version 26. Add an explicit CancellationContext return type to Server.createContext so declaration generation uses the existing exported type instead of an unnameable inferred AbortSignal type.
Runtime behavior, consumer Node requirements, and runtime and peer dependency ranges stay unchanged. Include an @tus/server patch changeset for the named declaration boundary.
The upgrade-specific compatibility script, fixture, and workflow have been removed. Existing build/lint and test CI validates the revised PR. Previous one-off packed-package comparisons found no new diagnostics on TypeScript 5.8 with Node 20 and 22; their existing srvx baseline errors were unchanged. Those historical checks are not a claim that the current head has passed CI.