Update all of typescript-eslint 5.32.0 → 6.21.0 (major) #1296
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
subzero10
changed the title
depfu
bot
force-pushed
the
depfu/update/npm/group/typescript-eslint-6.21.0
branch
from
13bf3aa to
1a6a62c
Compare
depfu
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
✳️ @typescript-eslint/eslint-plugin (5.32.0 → 6.21.0) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
✳️ @typescript-eslint/parser (5.59.9 → 6.21.0) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Sorry, we couldn't find anything useful about this release.
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
3.4.3
3.4.2
3.4.1
3.4.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 23 commits:
chore: release 3.4.3 (#57)chore: Add back add-to-triage (#59)chore: standardize npm script names (#55)chore: update `typedef` in build keys template (#58)chore: Remove add-to-triage (#56)chore: release 3.4.2 (#51)chore: Add PRs to triage (#54)ci: generate provenance statements when release (#53)docs: remove `release` script reference from README (#52)docs: fix spelling mistakes (#50)chore: release 3.4.1 (#49)chore: set up release-please (#48)fix: correct types for node16 resolution (#47)ci: run tests on Node.js v20 (#45)3.4.0Build: changelog update for 3.4.0fix: remove useless sourcemap url (fixes #43) (#44)chore: add triage action (#42)ci: add Node v19 (#41)chore: update github actions and add funding field (#40)build: add node v18 (#39)feat: add `JSXSpreadChild` and tool to build keys out of AST definitions (#36)docs: update badges (#37)Release Notes
5.3.0
5.2.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 31 commits:
5.3.1: #108: remove BOM before processing .gitignore rules5.3.0: #105Merge pull request #105 from DamianGlowala/patch-1Update index.d.tstest: rollback tap for the breaking changeMerge pull request #103 from kaelzhang/dependabot/npm_and_yarn/tap-18.5.3Bump tap from 16.3.9 to 18.5.3test/typescript: add more tests for interface Ignorechore: upgrade dev deps#94: upgrade mkdirp -> 3.0.0Merge pull request #93 from kaelzhang/dependabot/npm_and_yarn/rimraf-5.0.0Bump rimraf from 4.4.1 to 5.0.0Merge pull request #92 from kaelzhang/dependabot/npm_and_yarn/typescript-5.0.2Bump typescript from 4.9.5 to 5.0.2test: update git actions: since ignore are node-version-agnostic, so only test on node LTStest: since ignore are node-version-agnostic, so only test on node LTSchore: upgrade dev dependencies, fixes #85, fixes #89, fixes #86Create dependabot.yml5.2.4: README: update github action badgetest/coverage: do not force test coverage on windows since it is quite hard to ignore different lines for linux and windowstest/coverage: remove the buggy "istanbul ignore next" (nyc @15.1.0)test: another test cases related to #57dev: upgrade dev dependenciestest: remove timeout setting for git-check-ignore5.2.3: fixes #57: fixes normal single / consecutive asterisks#57: test: support test.only#81: fixes windows test cases#81: fixes windows test cases5.2.2: fixes #81: invalid single trailing backslash should not throw5.2.1: fixes typo in the example of "backslash hash", related to #83#76: add test case🆕 @eslint-community/eslint-utils (added, 4.4.0)
🆕 @eslint-community/regexpp (added, 4.10.0)
🆕 @types/semver (added, 7.5.8)
🆕 graphemer (added, 1.4.0)
🆕 ts-api-utils (added, 1.3.0)
🗑️ eslint-scope (removed)
🗑️ estraverse (removed)
🗑️ tsutils (removed)
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