Update dependency ajv to v8.20.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ajv (source)	8.17.1 → 8.20.0

---

Release Notes

ajv-validator/ajv (ajv)

v8.20.0

Compare Source

What's Changed

• fix: add support for node 22/24, drop node 16/21 by @​jasoniangreen in #​2580
• fix: add ES2022.RegExp for RegExpIndicesArray by @​SignpostMarv in #​2604

Full Changelog: ajv-validator/ajv@v8.19.0...v8.20.0

v8.18.0

Compare Source

What's Changed

• feat: allow tree-shaking by adding "sideEffects": false to package.json by @​josdejong in #​2480
• fix: #​2482 Infinity and NaN serialise to null by @​jasoniangreen in #​2487
• fix: small grammatical error in managing-schemas.md by @​monteiro-renato in #​2508
• fix: typos in schema-language.md by @​monteiro-renato in #​2507
• fix(pattern): use configured RegExp engine with $data keyword to mitigate ReDoS attacks (CVE-2025-69873) by @​epoberezkin in #​2586

New Contributors

• @​josdejong made their first contribution in #​2480
• @​monteiro-renato made their first contribution in #​2508

Full Changelog: ajv-validator/ajv@v8.17.1...v8.18.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 3am on Monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @ajna/pagination@1.4.19
npm error Found: typescript@5.9.3
npm error node_modules/typescript
npm error   dev typescript@"5.9.3" from the root project
npm error   peerOptional typescript@">= 4.7.4" from @puppeteer/browsers@1.4.6
npm error   node_modules/@puppeteer/browsers
npm error     @puppeteer/browsers@"1.4.6" from puppeteer-core@20.9.0
npm error     node_modules/lighthouse/node_modules/puppeteer-core
npm error       puppeteer-core@"^20.8.0" from lighthouse@10.4.0
npm error       node_modules/lighthouse
npm error         lighthouse@"^10.4.0" from @wordpress/e2e-test-utils-playwright@0.26.0
npm error         node_modules/@wordpress/e2e-test-utils-playwright
npm error   6 more (@wordpress/eslint-plugin, cosmiconfig, puppeteer-core, ...)
npm error
npm error Could not resolve dependency:
npm error peer react-scripts@"5.0.1" from @ajna/pagination@1.4.19
npm error node_modules/@ajna/pagination
npm error   @ajna/pagination@"1.4.19" from the root project
npm error
npm error Conflicting peer dependency: typescript@4.9.5
npm error node_modules/typescript
npm error   peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm error   node_modules/react-scripts
npm error     peer react-scripts@"5.0.1" from @ajna/pagination@1.4.19
npm error     node_modules/@ajna/pagination
npm error       @ajna/pagination@"1.4.19" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-05-25T02_04_50_192Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-25T02_04_50_192Z-debug-0.log