Skip to content
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.

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

fix: revert eslint-plugin-json upgrade from v4 to v3 for eslint v8 comp #317

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

michaeljaltamirano
Copy link
Contributor

From https://github.com/azeemba/eslint-plugin-json: If you are using eslint v9 or newer, use eslint-plugin-json v4 or newer. The "legacy" package was added in v4, but v4 only supports flat configs.

…mpatibility

Revert "fix(deps): update dependency eslint-plugin-json to v4"

This reverts commit 5c3ee8b.
Copy link

github-actions bot commented Aug 3, 2024

Release notes preview

Below is a preview of the release notes if your PR gets merged.


9.0.10 (2024-08-03)

Bug Fixes

  • revert eslint-plugin-json upgrade from v4 to v3 for eslint v8 compatibility (b2fc2f7)

@michaeljaltamirano
Copy link
Contributor Author

I am no longer seeing this error in manual testing, I think the issue is both packages in Schumacher need to be updated in sync.

https://github.com/turo/web-schumacher-app/actions/runs/10917224321/job/30301410817 shows recommended-legacy not existing.

https://github.com/turo/web-schumacher-app/actions/runs/10917221063/job/30301768518 shows /recommended not existing.

Both versions need to be updated at the same time to resolve this issue, it seems. Opening a manual PR for this work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant