Bump srvx from 0.8.9 to 0.11.13

[dependabot]

• Inspect current branch state and recent fix commits
• Re-check CI/build failures for this PR
• Read the srvx Node guide and inspect srvx typings/API usage
• Revert any overreaching test changes if they are unnecessary
• Implement the correct minimal srvx compatibility fix
• Run targeted validation and final review/security checks
• Reply to the PR comment with the addressing commit hash

[changeset-bot]

🦋 Changeset detected

Latest commit: 78907ee

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@tus/server	Patch

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	srvx@​0.8.9 ⏵ 0.11.15	+1	+2	-3	-1

View full report

[Murderlon]

@copilot fix the build errors that were introduced by upgrading srvx

[Copilot]

@copilot fix the build errors that were introduced by upgrading srvx

Addressed in ebc738e. The srvx 0.11 upgrade now builds again by narrowing toNodeHandler() to the HTTP/1 request/response types used by server.handle(), and I updated the preserved-request test to use a real Node HTTP server because the old mock response no longer matches srvx’s expectations. I also re-ran npm run build, npm run format:check, npm run lint, and the server-focused test suite successfully.

[Murderlon]

@copilot I don't like that you changed the tests beyond just type changes and adding as assertion to the handler also can't be the correct solution here. Look into it again and read https://srvx.h3.dev/guide/node before implementing.

[Copilot]

@copilot I don't like that you changed the tests beyond just type changes and adding as assertion to the handler also can't be the correct solution here. Look into it again and read https://...

Addressed in e8af722. I replaced the toNodeHandler() assertion with the srvx-documented Node path by using NodeRequest + sendNodeResponse() in server.handle(), and I reverted the broader test rewrite. The only test changes left are the minimal node-mocks-http shims needed for rawHeaders and off, which srvx now reads in its Node adapter.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• srvx.h3.dev
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[dependabot]

A newer version of srvx exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.