Skip to content

[Snyk] Security upgrade ajv from 5.2.3 to 8.18.0 #501

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
acatl wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade ajv from 5.2.3 to 8.18.0 #501

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/data-point/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@
"lib/"
],
"dependencies": {
"ajv": "5.2.3",
"ajv": "8.18.0",

Copilot AI Feb 16, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The upgrade from ajv 5.2.3 to 8.18.0 introduces multiple breaking changes that are not addressed in this PR:

  1. Removed v5 option: The v5: false option used throughout the codebase (in factory.test.js, schema.js, and integrations.js) was removed in ajv v7. This option no longer exists and will be ignored or may cause errors.

  2. Error format changes: ajv v7+ changed the error object structure - the dataPath property was renamed to instancePath. The test snapshots explicitly check for dataPath in error objects, which will cause test failures.

  3. JSON Schema draft support: ajv v6+ dropped support for JSON Schema draft-04. The code should verify that all schemas are compatible with draft-06 or later.

  4. Strict mode by default: ajv v7+ enables strict schema mode by default, which may reject previously valid schemas. The code may need to pass strict: false in the Ajv constructor options if relying on lenient schema validation.

  5. Node.js version requirement: ajv v8+ requires Node.js 12 or later, but package.json specifies "node": ">=8".

The code in lib/entity-types/entity-schema/factory.js and resolve.js needs to be updated to handle these changes, and test snapshots need to be regenerated. Additionally, the data-point-service package also uses ajv 5.2.3 and should be upgraded in coordination with this change.

Copilot uses AI. Check for mistakes.
"debug": "3.x",
"deep-freeze": "0.0.1",
"json-stringify-safe": "^5.0.1",
Expand Down
Loading