Update Types packages (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/node (source)	20.19.39 → 24.12.2
@types/sinon (source)	17.0.4 → 21.0.1
@​types/uuid	10.0.0 → 11.0.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • Between 07:00 AM and 04:59 PM, only on Monday, Tuesday, Wednesday, and Thursday (* 7-16 * * 1,2,3,4)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sagzy]

@codex review

[Copilot]

Pull request overview

Updates TypeScript type definition packages via Renovate to newer major versions, refreshing Node/Sinon/UUID typings used by the ActivityPub TypeScript codebase.

Changes:

• Bump @types/node from 20.19.33 to 24.10.13
• Bump @types/sinon from 17.0.4 to 21.0.0
• Bump @types/uuid from 10.0.0 to 11.0.0 (and update lockfile transitive deps accordingly)

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 2 comments.

File	Description
package.json	Updates the pinned major versions of the @types/* devDependencies.
yarn.lock	Reflects the updated @types/* resolutions and new transitive dependencies (notably uuid@*).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

@types/node is being bumped to a Node 24.x typing set while the repo’s runtime Node version appears to be 22.22.0 (see .nvmrc and Dockerfile base image). This can make TypeScript accept newer Node APIs that won’t exist at runtime and may introduce subtle type mismatches; consider pinning @types/node to the supported Node major (e.g., 22.x) or updating the repo’s Node runtime/version policy in the same change.

Suggested change

	"@types/node": "24.10.13",
	"@types/node": "22.10.2",

[Copilot]

Updating @types/uuid to 11.0.0 introduces a new transitive dependency on uuid "*", which in the lockfile resolves to an additional uuid@13.0.0 alongside the existing direct dependency uuid@10.0.0. This increases dependency surface area and can lead to mismatched runtime vs. typing expectations; consider either keeping @types/uuid at a version that doesn’t pull uuid, adding a Yarn resolution to force the transitive uuid to the same version as your direct dependency, or upgrading the direct uuid dependency to match.

Suggested change

	"@types/uuid": "11.0.0",
	"@types/uuid": "10.0.0",

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 861752ed81

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Align @types/node with deployed Node major

Updating @types/node to 24.x makes the compiler accept Node 24-only APIs while this service is still built and run on Node 22 (Dockerfile line 1), so type checks can now pass for code that will fail at runtime in production. Keeping Node typings on the same major as the deployed runtime prevents this class of false-negative compatibility checks.

Useful? React with 👍 / 👎.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: CICD
• Failed Step: Run Tests
• Run: View failed run
  What failed: Cannot find type definition file for 'uuid' in TypeScript build
  Why: The TypeScript build failed because it could not find the type definition file for the 'uuid' package. This is a code issue, as the project is missing the necessary type definitions for a dependency.
  Action:
  The author should ensure that the 'uuid' type definitions are properly installed and imported in the project. This can be done by installing the '@types/uuid' package as a development dependency.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: CICD
• Failed Step: Run Tests
• Run: View failed run
  What failed: Cannot find type definition file for 'uuid' - missing dependency
  Why: The root cause is a missing type definition file for the 'uuid' dependency, which is causing a TypeScript compilation error. This is a code issue that the author should fix by ensuring the necessary type definitions are installed.
  Action:
  The author should check the project's dependencies and ensure the 'uuid' type definitions are properly installed. They may need to add a dependency on the '@types/uuid' package.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: CICD
• Failed Step: Run Tests
• Run: View failed run
  What failed: TypeScript type errors
  Why: The failure is caused by a code issue that needs to be fixed in this PR.
  Action:
  Check the error message and fix the issue in your code.

[ErisDS]

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

• Workflow: CICD
• Failed Step: Run Tests
• Run: View failed run
  What failed: TypeScript type errors
  Why: The failure is caused by a code issue that needs to be fixed in this PR.
  Action:
  Check the error message and fix the issue in your code.