build(deps): update dependency @yarnpkg/core to v4.7.0 (main)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@yarnpkg/core (source)	4.6.0 → 4.7.0

---

Release Notes

yarnpkg/berry (@​yarnpkg/core)

v4.7.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• 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 an artifact 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: pnpm-lock.yaml

Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 81, reused 0, downloaded 0, added 0
Progress: resolved 140, reused 0, downloaded 0, added 0
Progress: resolved 195, reused 0, downloaded 0, added 0
Progress: resolved 249, reused 0, downloaded 0, added 0
 ERR_PNPM_NO_MATURE_MATCHING_VERSION  Version 4.6.0 (released 2 days ago) of @smithy/node-http-handler does not meet the minimumReleaseAge constraint

This error happened while installing the dependencies of @smithy/util-stream@4.5.23

The latest release of @smithy/node-http-handler is "4.6.0". Published at 4/20/2026

If you need the full list of all 84 published versions run "pnpm view @smithy/node-http-handler versions".

If you want to install the matched version ignoring the time it was published, you can add the package name to the minimumReleaseAgeExclude setting. Read more about it: https://pnpm.io/settings#minimumreleaseageexclude

[jamietanna]

Interesting - I guess there's a range used for that transitive dependency, and it's not strict enough to enforce that we'll only pull one that fits within minimumReleaseAge (on the pnpm side)