Conformance changelog

• Support for Turborepo v2 configuration

• Update dependencies listed in file
• Update rule to not treat as just a client dependency

• Adds a file listing third party licenses

• Update rule to highlight the awaited call expression instead of the entire function

• Update rule logic for detecting duplicate allowlist entries based on the details field

This patch update has the following changes:

• Optimize checking allowlists for existing Conformance issues
• Isolate some work by moving it to a worker thread
• Fix error when trying to parse empty JavaScript/TypeScript files

This patch update has the following changes:

• Parse ESLint JSON config with a JSONC parser
• Fix retrieving latest version of CLI during

This patch update has the following changes:

• Fix updating allowlist files when entries conflict or already exist

This minor update has the following changes:

• Replace Next.js rule with
• Fix showing error messages for rules
• Update allowlist entry details for

This minor update has the following changes:

• Ensure in-memory objects are cleaned up after each run
• Fix detection of Next.js apps in certain edge cases
• Bump dependencies for performance and security

This patch update has the following changes:

• Fix the init command for Yarn classic (v1)
• Update AST caching to prevent potential out of memory issues
• Fix requesting git authentication when sending Conformance metrics

This minor update has the following changes:

• Support non-numeric Node version numbers like in .
• Add version range support for custom rules.
• Updates dependencies for performance and security.

New rules:

• . Requires that all exported functions have JSDoc comments.

This minor update captures and sends Conformance runs metrics to Vercel. Your team will be able to view those metrics in the Vercel dashboard.

The following rules also include these fixes:

• : Improved error messaging.
• : Improved error messaging.

This minor update introduces multiple new rules, fixes and improvements for existing rules and the CLI, and updates to some dependencies for performance and security.

Notably, this release introduces a new flag. This is used by the CLI and will be used in future metrics as a mechanism to opt-out of further tracking of this issue.

The following new rules have been added:

• : Disallows the usage of object spreading in JSX components.

The following rules had fixes and improvements:

• : Additional cases are now covered by this rule.
• : Multiple issues in the same file are no longer reported as a single issue.
• : Multiple issues in the same file are no longer reported as a single issue.
• : Multiple issues in the same file are now differentiated by the package name and the location of the entry in .

This minor update introduces a new rule and improvements to our telemetry.

The following new rules have been added:

• : Disallows using comparisons due to risk of false negatives.

This minor update introduces multiple new rules, fixes and improvements for existing rules and the CLI, and updates to some dependencies for performance and security.

The following new rules have been added:

• : Requires allowlist entries for any usage of environment variables.
• : Prevents the use of script in package for performance reasons.
• : Requires that all and have a prefix.

The following rules had fixes and improvements:

• : Lowercase files are now considered valid.
• : Resolved an issue preventing this rule from correctly reporting issues.
• : Detection logic now handles template strings alongside string literals.
• The custom rule type now supports being defined in rule configuration.

This minor update introduces new rules to improve Next.js app performance, resolves an issue where TypeScript's wasn't respected when traversing files, and fixes an issue with dependency traversal which caused some rules to return false positives in specific cases.

The following new rules have been added:

• : Requires explicitly setting the route segment option for Next.js pages and routes.
• : Prevents the use of tags inline, which can negatively impact the performance of both browser and server rendering.

This patch updates some Conformance dependencies for performance and security, and improves handling of edge case for both and .

This minor update introduces a new rule, and improvements to both and .

The following new rules have been added:

• : Requires that workspaces have a valid Node.js version file ( or ) file defined.

This minor update introduces new rules to improve Next.js app performance, enhancements to the CLI output, and improvements to our telemetry. While telemetry improvements are not directly user-facing, they enhance our ability to monitor and optimize performance.

The following new rules have been added:

• : Ensures that the exported Next.js page component and its transitive dependencies are not asynchronous, as that blocks the rendering of the page.
• : Ensures that the exported Next.js layout component and its transitive dependencies are not asynchronous, as that can block the rendering of the layout and the rest of the page.
• : Requires using native which Next.js polyfills, removing the need for third-party fetch libraries.
• : Requires using (when possible), which optimizes fonts for improved privacy and performance.
• : Requires that is used for all images for improved performance.
• : Requires that is used for all scripts for improved performance.

Initial release of Conformance.