Update dependency domain-browser to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
domain-browser	4.23.0 -> 5.5.0

---

Release Notes

bevry/domain-browser (domain-browser)

v5.5.0

Compare Source

• Updated dependencies, base files, and editions using boundation

v5.4.0

Compare Source

• Updated dependencies, base files, and editions using boundation

v5.3.0

Compare Source

• Updated dependencies, base files, and editions using boundation

v5.2.0

Compare Source

• Updated dependencies, base files, and editions using boundation

v5.1.0

Compare Source

• Updated dependencies, base files, and editions using boundation

v5.0.0

Compare Source

• Updated dependencies, base files, and editions using boundation
• Minimum required Node.js version changed from node: >=10 to node: >=4 adapting to ecosystem changes

v4.23.0

Compare Source

• Updated dependencies, base files, and editions using boundation
• Updated license from MIT to Artistic-2.0

---

Configuration

📅 Schedule: 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 has been generated by Mend Renovate. View repository job log here.

[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

[19:06:14.724] INFO (9): Installing tool node v20.10.0...
v20.10.0
10.2.3
0.22.0
[19:06:17.394] INFO (9): Installed tool node in 2.6s.
[19:06:18.031] INFO (52): Installing tool pnpm v8.11.0...
8.11.0
[19:06:19.426] INFO (52): Installed tool pnpm in 1.3s.
Scope: all 21 workspace projects
Progress: resolved 0, reused 1, downloaded 0, added 0
.                                        |  WARN  deprecated @babel/[email protected]
packages/next                            |  WARN  deprecated @babel/[email protected]
packages/next                            |  WARN  deprecated @babel/[email protected]
packages/next                            |  WARN  deprecated @babel/[email protected]
packages/next                            |  WARN  deprecated @types/[email protected]
Progress: resolved 262, reused 233, downloaded 14, added 0
/tmp/worker/c7f39e/812a98/repos/github/X-oss-byte/Nextjs/packages/third-parties:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/next/-/next-13.5.0.tgz: Not Found - 404

This error happened while installing a direct dependency of /tmp/worker/c7f39e/812a98/repos/github/X-oss-byte/Nextjs/packages/third-parties

No authorization header was set for the request.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f5b6f75

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.

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