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
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
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-markdown (^2.0.0 → ^3.0.0) · Repo · Changelog
Release Notes
3.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 15 commits:
3.0.0Build: changelog update for 3.0.0chore: add node v18 (#205)feat!: drop node v8 and v10 (#203)ci: update github actions (#207)ci: Work around npm behavior changes to fix CI on main (#206)docs: update badges (#202)chore: add tests for ESLint 8 (#195)chore: Check for package.json in examples (#200)test: test with `ESLint` instead of `CLIEngine` when available (#198)ci: use node `v16` (#199)chore: update `devDependencies` (#197)chore: test all supported ESLint versions (#196)Chore: ignore pnpm-lock.yaml (#193)Chore: use `actions/setup-node@v2` in CI (#192)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