fix(security): Bump ajv from 8.17.1 to 8.18.0

[sumi-mathew]

Description

Bump ajv from 8.17.1 to 8.18.0 to address CVE-2025-69873

Test Plan

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.
• If adding new dependencies, verified they have an OpenSSF Scorecard score of 5.0 or higher (or obtained explicit TSC approval for lower scores).

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

Security Changes
* Upgrade ajvto 8.18.0 in response to `CVE-2025-69873 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-69873>`_. 

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the prestodb UI’s ajv dependency to version 8.18.0 in yarn.lock to address a reported security vulnerability (CVE-2025-69873), ensuring the lockfile is in sync with the new secure version.

File-Level Changes

Change	Details	Files
Upgrade the ajv dependency used by the Presto UI to version 8.18.0 to remediate a security vulnerability.	Update the ajv entry in yarn.lock from 8.17.1 to 8.18.0, including its resolved tarball URL and integrity hash as generated by Yarn Ensure any transitive sub-entries related to the ajv package in yarn.lock are aligned with the new version so dependency resolution is consistent	presto-ui/src/yarn.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• In the release notes, fix the typo and spacing in * Upgrade ajvto 8.18.0... so it reads cleanly (e.g., ajv to 8.18.0) and ensure the CVE link formatting matches the project's usual reST/Markdown style.
• Since only yarn.lock is changed, double-check whether package.json (or other dependency manifests) also needs an explicit ajv version bump to avoid the lockfile change being overwritten by future installs.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In the release notes, fix the typo and spacing in `* Upgrade ajvto 8.18.0...` so it reads cleanly (e.g., `ajv to 8.18.0`) and ensure the CVE link formatting matches the project's usual reST/Markdown style.
- Since only `yarn.lock` is changed, double-check whether `package.json` (or other dependency manifests) also needs an explicit ajv version bump to avoid the lockfile change being overwritten by future installs.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[unidevel]

LGTM

[imsayari404]

LGTM

[yhwang]

Thanks
/LGTM