Update eslint-plugin-prettier 4.0.0 → 5.0.0 (major) #180
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint-plugin-prettier (4.0.0 → 5.0.0) · Repo · Changelog
Release Notes
5.0.0
4.2.1
4.2.0
4.1.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 38 commits:
chore: release eslint-plugin-prettier (#569)
chore: bump deps, use pnpm instead (#568)
chore: release eslint-plugin-prettier (alpha) (#566)
fix: compatibility with prettier@3 without plugins (#564)
chore: release eslint-plugin-prettier (alpha) (#553)
fix: add missing dependency `synckit` (#548)
chore: add missing worker.js into files
chore: release eslint-plugin-prettier v5.0.0-alpha.0 (#517)
feat!: bump eslint, node and prettier versions, add types support (#508)
ci use pull_request_target event instead
docs: remove `Sponsors` and `Backers` section from README.md (#504)
chore: update @1stg/remark-config usage in favor of @1stg/config package
chore: release eslint-plugin-prettier (#496)
ci: downgrade eslint-plugin-svelte for node 12
ci: fix incorrect commit message nad PR title
chore: add FUNDING.yml
docs: add changeset for releasing
docs: add Sponsors and Backers sections
chore: use eslint-plugin-svelte v2 (#487)
chore: release prettier-plugin-svelte v4.2.1 (#486)
chore: reuse prettierRcOptions instead of resolveConfig again (#485)
ci: perf on CI
chore: use changeset publish instead
chore: release prettier-plugin-svelte v4.2.0 (#484)
docs: notice `Svelte` support
ci: add missing commit message template
chore: do not format .svelte fixtures unexpectedly
feat: support svelte out of box (#483)
docs: use correct json content in md (#480)
chore: enable some linter rules and tools (#478)
chore: use changesets for version management (#477)
chore: release eslint-plugin-prettier v4.1.0 (#475)
feat: skip processing code blocks on specific languages like `stylelint-prettier` (#415)
build(deps): Bump minimist from 1.2.5 to 1.2.6 (#464)
build(deps-dev): Bump graphql from 15.5.1 to 15.7.2 (#442)
build(deps-dev): Bump @graphql-eslint/eslint-plugin from 2.3.0 to 2.4.0 (#444)
chore(CI): add tests for ESLint 8 (#428)
README.md: HTTP => HTTPS (#443)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands