fix(deps): update dependency @portabletext/react to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@portabletext/react	6.2.0 → 7.0.1

---

Release Notes

portabletext/react-portabletext (@​portabletext/react)

v7.0.1

Compare Source

Patch Changes

• #​336 282c73d Thanks @​stipsan! - Give default Portable Text components proper function names for React DevTools and React Compiler coverage.

v7.0.0

Compare Source

Major Changes

• #​333 87a9b1e Thanks @​stipsan! - <PortableText> now ships as two builds selected by export conditions: the default build is optimized with React Compiler auto-memoization, and an uncompiled build serves the react-server condition, since React Server Components refuse to load compiled output (facebook/react#31702):

  ".": {
    "types": "./dist/index.d.ts",
    "react-server": "./dist/index.react-server.js",
    "default": "./dist/index.js"
  }

  There are no API changes. Client components and SSR get the compiled build, with finer-grained memoization than the manual useMemo calls it replaces, and server components render the same source uncompiled — they render exactly once, so memoization can never pay off there.

  BREAKING: React 19 is now required (peerDependencies.react is ^19) — the compiled build loads react/compiler-runtime, which only exists in React 19. Stay on @portabletext/react@6 if you are on React 18.

---

Configuration

📅 Schedule: (in timezone Europe/Oslo)

• Branch creation
  • "before 6am on Saturday"
• 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 has been generated by Mend Renovate using a preset from . View repository job log here

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3575c65

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR