Update prettier-eslint 15.0.1 → 16.1.1 (major) #187
Closed
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?
✳️ prettier-eslint (15.0.1 → 16.1.1) · Repo · Changelog
Release Notes
16.1.1
16.1.0
16.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
chore: release prettier-eslint (#941)
fix: @changesets/cli and @types/eslint should be devDependencies (#940)
chore: release prettier-eslint v16.1.0 (#939)
Create FUNDING.yml
feat!: bump all (dev)Dependencies, drop node < 16.10 (#938)
docs: update build status badge
chore: reformat
docs: remove unrelated CHANGELOG
ci: use `npm start release` instead
chore: release prettier-eslint v16.0.0 (#937)
chore: migrate to changesets
feat! add support for prettier v3 (#901)
update vs-code plugin (#825)
Completing the missing LogLevel values 'silent' (#788)
chore: upgrade husky to v8 (#801)
build(deps): bump vue-eslint-parser from 8.3.0 to 9.1.0 (#783)
build(deps-dev): bump prettier-eslint-cli from 5.0.1 to 7.0.0 (#768)
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