chore(deps): update dependency react-cosmos-plugin-rspack to v3 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
react-cosmos-plugin-rspack	2.0.2 → 3.0.0

---

Release Notes

birchill/react-cosmos-plugin-rspack (react-cosmos-plugin-rspack)

v3.0.0

Compare Source

⚠ BREAKING CHANGES

• Requires rspack 2

Features

• update to rspack 2 (0df2a0c)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

🔕 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
[ERR_PNPM_NO_MATURE_MATCHING_VERSION] Version 3.0.0 (released 6 hours ago) of react-cosmos-plugin-rspack does not meet the minimumReleaseAge constraint

This error happened while installing a direct dependency of /tmp/renovate/repos/github/birchill/10ten-ja-reader

The latest release of react-cosmos-plugin-rspack is "3.0.0". Published at 5/7/2026 4:37:20 AM

If you need the full list of all 17 published versions run "pnpm view react-cosmos-plugin-rspack 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