fix(deps): update website

[squiggler-app]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/react-dom (source)	^19.2.4 → ^19.2.5
next (source)	^16.3.1 → ^16.3.3

---

Release Notes

vercel/next.js (next)

v16.3.3

Compare Source

This release contains security fixes for the following advisories:

Critical:

• Unauthenticated Remote Code Execution on windows-hosted servers
• Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used

---

Configuration

📅 Schedule: (UTC)

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

---

Note

Low Risk
Patch-level dependency and lockfile updates for the website; main effect is picking up Next.js security fixes with limited behavioral surface beyond the framework patch.

Overview
Updates website dependencies: Next.js ^16.3.1 → ^16.3.3 (lockfile moves from 16.3.2 to 16.3.3, including @next/env and platform SWC packages) and @types/react-dom ^19.2.4 → ^19.2.5, with matching pnpm-lock.yaml resolution updates for nextra / nextra-theme-docs.

Adds minimumReleaseAgeExclude entries in pnpm-workspace.yaml for next@16.3.3 and @types/react-dom@19.2.5 so these versions are not held back by the workspace minimum-release-age policy (typical for urgent or bot-driven bumps).

No application source changes—docs site only.

^{Reviewed by Cursor Bugbot for commit 5cffcae. Bugbot is set up for automated code reviews on this repo. Configure here.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5cffcae

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
react-rx	Ready	Preview	Aug 26, 2026 7:29pm

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​next@​16.3.3

View full report

[stipsan]

@copilot add any dep to pnpm minimumReleaseAgeExcemptions that you need in order for the install to succeed, use pnpm dedupe instead of pnpm install, then commit the pnpm-lock.yaml and pnpm-workspace.yaml

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 39e83c6. Configure here.}

[stipsan]

@copilot add any dep to pnpm minimumReleaseAgeExcemptions that you need in order for the install to succeed, use pnpm dedupe instead of pnpm install, then commit the pnpm-lock.yaml and pnpm-workspace.yaml

[Copilot]

@copilot add any dep to pnpm minimumReleaseAgeExcemptions that you need in order for the install to succeed, use pnpm dedupe instead of pnpm install, then commit the pnpm-lock.yaml and `pnpm-wor...

Addressed in 5cffcae: added release-age exclusions needed for the updated deps and ran pnpm dedupe (as requested). pnpm-lock.yaml had no diff after dedupe; pnpm-workspace.yaml was updated and committed.

@copilot add any dep to pnpm minimumReleaseAgeExcemptions that you need in order for the install to succeed, use pnpm dedupe instead of pnpm install, then commit the pnpm-lock.yaml and `pnpm-wor...

Addressed in 5cffcae: added release-age exclusions needed for the updated deps and ran pnpm dedupe (as requested). pnpm-lock.yaml had no diff after dedupe; pnpm-workspace.yaml was updated and committed.

[squiggler-app]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.