fix(deps): update dependency toml to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
toml	^3.0.0 → ^5.0.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

BinaryMuse/toml-node (toml)

v5.0.0

Compare Source

=====================

• Breaking: Integers outside JavaScript's safe range (beyond ±Number.MAX_SAFE_INTEGER) now throw a parse error instead of silently returning a rounded value (#​28). Opt in to lossless handling of the full 64-bit range with toml.parse(input, { bigint: true }), which returns all integer values as BigInt.
• Breaking: Integers outside TOML's 64-bit signed integer range now throw a parse error in either mode, as required by the spec. Previously they were silently rounded.

v4.3.0

Compare Source

=====================

• Add opt-in Temporal support via toml.parse(input, { useTemporal: true }), mapping offset date-times to Temporal.ZonedDateTime and local date-times/dates/times to Temporal.PlainDateTime/PlainDate/PlainTime. An implementation can be supplied via the temporal option on runtimes without a Temporal global. (#​69)

v4.2.0

Compare Source

=====================

• Address security advisory GHSA-82x6-q7mm-w9cf (CVE pending), in which deeply nested arrays or inline tables could overflow the call stack and crash the process with an uncatchable RangeError. Nesting is now bounded (default 500 levels), and input past the limit throws a normal parse error. The limit is configurable via toml.parse(input, { maxDepth }).

v4.1.2

Compare Source

=====================

• Address CVE-2026-63376, in which a specially crafted TOML string could pollute Object.prototype process-wide.

v4.1.1

Compare Source

=====================

• Increase performance ~5x (#​68)

v4.1.0

Compare Source

=====================

• Add spec v1.1.0 support (#​67)

v4.0.1

Compare Source

=====================

• Minor packaging changes

v4.0.0

Compare Source

=====================

• Modernize tooling and support TOML v1.0.0 spec (#​66)

---

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• 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.

[github-actions]

e18e dependency analysis

No dependency warnings found.

[pkg-pr-new]

Open in StackBlitz

@netlify/build

npm i https://pkg.pr.new/@netlify/build@7163

@netlify/build-info

npm i https://pkg.pr.new/@netlify/build-info@7163

@netlify/cache-utils

npm i https://pkg.pr.new/@netlify/cache-utils@7163

@netlify/config

npm i https://pkg.pr.new/@netlify/config@7163

@netlify/edge-bundler

npm i https://pkg.pr.new/@netlify/edge-bundler@7163

@netlify/functions-utils

npm i https://pkg.pr.new/@netlify/functions-utils@7163

@netlify/git-utils

npm i https://pkg.pr.new/@netlify/git-utils@7163

@netlify/headers-parser

npm i https://pkg.pr.new/@netlify/headers-parser@7163

@netlify/api

npm i https://pkg.pr.new/@netlify/api@7163

@netlify/nock-udp

npm i https://pkg.pr.new/@netlify/nock-udp@7163

@netlify/opentelemetry-sdk-setup

npm i https://pkg.pr.new/@netlify/opentelemetry-sdk-setup@7163

@netlify/opentelemetry-utils

npm i https://pkg.pr.new/@netlify/opentelemetry-utils@7163

@netlify/redirect-parser

npm i https://pkg.pr.new/@netlify/redirect-parser@7163

@netlify/run-utils

npm i https://pkg.pr.new/@netlify/run-utils@7163

@netlify/zip-it-and-ship-it

npm i https://pkg.pr.new/@netlify/zip-it-and-ship-it@7163

commit: a93d4d8

[renovate]

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.