⚠️ No Changeset found

Latest commit: e4a86d3

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.

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

Need update Branch protection rule when merge.

Seems only housekeeping, but Node 14/16 compatible tests are disabled?

but Node 14/16 compatible tests are disabled?

ESLint can't run on them https://github.com/prettier/eslint-plugin-prettier/actions/runs/13699233561/job/38308655951#step:6:28 . Suggestion?

but Node 14/16 compatible tests are disabled?

ESLint can't run on them prettier/eslint-plugin-prettier/actions/runs/13699233561/job/38308655951#step:6:28 . Suggestion?

We may need to downgrade eslint to v8 for Node 14/16 on CI?

eslint-plugin-prettier@5 is compatible with eslint v8/v9, so testing is still needed just like prettier itself?

https://github.com/prettier/prettier/blob/main/.github/workflows/prod-test.yml#L61

We may need to downgrade eslint to v8 for Node 14/16 on CI?

I can try, but do we have a plan to drop support? Since I didn't actually change the code, it should still work with ESLint 8, just not tested.

I can try, but do we have a plan to drop support? Since I didn't actually change the code, it should still work with ESLint 8, just not tested.

Personally I'd follow prettier's strategy instead of eslint's.

What means when prettier changes its engines support, eslint-plugin-prettier will follow.

All tested.

Thanks for your great work!