👷 Lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 4am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: playground/yarn.lock

! Corepack is about to download https://repo.yarnpkg.com/4.17.1/packages/yarnpkg-cli/bin/yarn.js

File name: yarn.lock

➤ YN0000: · Yarn 4.17.1
➤ YN0000: ┌ Resolution step
➤ YN0080: │ json-schema-to-typescript@bcaudan/json-schema-to-typescript#bcaudan/add-readonly-support: Request to 'https://github.com/bcaudan/json-schema-to-typescript.git' has been blocked because it doesn't match any of the patterns in 'approvedGitRepositories'
➤ YN0000: └ Completed in 3s 936ms
➤ YN0000: · Failed with errors in 3s 956ms

File name: e2e/app/yarn.lock

➤ YN0000: · Yarn 4.17.1
➤ YN0000: ┌ Resolution step
➤ YN0016: │ dd-trace@npm:6.10.0: All versions satisfying "6.10.0" are quarantined
➤ YN0000: └ Completed in 0s 530ms
➤ YN0000: · Failed with errors in 0s 559ms

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5da31531f7

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Avoid locking node-gyp 13 while Node 25 is pinned

When yarn test:e2e:init or yarn dev:init runs under the repo-pinned Node 25.9.0 environment, this lock now selects node-gyp@13.0.1; that release declares support for ^22.22.2 || ^24.15.0 || >=26.0.0, excluding Node 25, so any dd-trace native addon that falls back to a rebuild will run on an unsupported node-gyp toolchain. The previous 12.x lock, and the other project lockfiles, avoid that mismatch; keep this on 12.x or move the repo Node pin before refreshing these locks.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Do not lock an unavailable js-yaml release

In a clean cache, yarn test:e2e:init will need to fetch this exact tarball from the npm registry, but js-yaml@4.3.0 is no longer available there, so the lockfile now makes fresh E2E app installs fail before the build starts. Keep the resolution on an available ^4.1.0 version, such as the previous 4.1.x/4.2.x line, unless the registry entry is restored.

Useful? React with 👍 / 👎.