chore(devdeps): update dependency eslint-plugin-package-json to v0.56.3 #409

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

nx-cloud · 2025-09-07T14:03:59Z

View your CI Pipeline Execution ↗ for commit 9c04b25

Command	Status	Duration	Result
`nx affected -t build typecheck lint test e2e-ci`	❌ Failed	2m 35s	View ↗
`nx-cloud record -- nx format:check`	✅ Succeeded	1s	View ↗

☁️ Nx Cloud last updated this comment at 2025-10-02 19:10:51 UTC

coderabbitai · 2025-09-22T15:32:30Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

nx-cloud

Nx Cloud has identified a possible root cause for your failed CI:

The pull request updates eslint-plugin-package-json from version 0.30.0 to 0.56.3, a major version jump introducing numerous new validation rules for package.json files.

The failures occur because the updated plugin version includes new rules that were not present in the previous version:

require-description: Now requires all packages to have a description field
require-type: Now requires packages to specify a type field
valid-author: Enhanced validation requiring author fields to have a name property
valid-description: Enhanced validation ensuring descriptions are non-empty

These failures are classified as environment_state because:

The package.json files in the repository were not modified by this PR
The files were already "non-compliant" according to the new rules
The PR only updated the linting tool, which now detects pre-existing issues
The failures are a result of stricter tooling being introduced, not code changes

The repository's package.json files would need to be updated to comply with the new ESLint rules, but this should be done as a separate effort from the dependency update. The dependency update itself did not introduce any bugs or break any functionality - it merely revealed existing gaps in package.json metadata according to the new validation rules.

To resolve this, the team should either:

Update all package.json files to include the required fields
Configure the new rules to be warnings instead of errors
Disable specific rules that are not desired for this project
Pin the eslint-plugin-package-json version until the codebase can be updated

A code change would likely not resolve this issue, so no action was taken.

View in Nx Cloud ↗

_{⚙️ An Nx Cloud workspace admin can disable these reviews in workspace settings.}

renovate bot added the UPDATE-MINOR label Sep 7, 2025

renovate-approve bot approved these changes Sep 7, 2025

View reviewed changes

renovate bot force-pushed the renovate/eslint-plugin-package-json-0.x branch 3 times, most recently from 16daaef to 945cf75 Compare September 10, 2025 19:08