Update all of typescript-eslint: 5.52.0 → 5.54.0 (minor) #439
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @typescript-eslint/eslint-plugin (5.52.0 → 5.54.0) · Repo · Changelog
Release Notes
5.54.0
5.53.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 21 commits:
chore: publish v5.54.0chore: fix npm tag publishing for v6 branchfix(typescript-estree): check for relative/root paths in printing file path errors (#6491)chore: hardcode v6 branch name in v6 canary publish (#6512)chore: increase wait-for-netlify max_timeout to 5 minschore(website): correct crash when switching to dark/light mode in playground (#6496)chore(deps): update nx to v15.7.2 (#6507)chore(deps): update probablyup/wait-for-netlify-action action to v3.4.0 (#6502)fix(website): corect playground build issue (#6506)feat(eslint-plugin): [promise-function-async] check for promises in implicit return types (#6330)chore: fix ci token (#6503)chore: publish v5.53.0chore: use read-only token for nx cloud in source control (#6501)chore: run website tests against netlify deployment (#6212)chore(deps): update nx to v15.7.1 (#6482)chore(deps): update dependency lerna to v6.5.1 (#6480)feat(typescript-estree): expose a wrapper cache clearing function for advanced usecases (#6476)feat(eslint-plugin): [consistent-generic-constructors] handle default parameters (#6484)feat(eslint-plugin): [no-mixed-enums] add rule (#6102)docs(website): fix typed rules heading link in custom rule docs (#6460)docs(eslint-plugin): explicit-function-return-type: missing allowFunctionsWithoutTypeParameters sections (#6475)✳️ @typescript-eslint/parser (5.52.0 → 5.54.0) · Repo · Changelog
Release Notes
5.54.0
5.53.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 21 commits:
chore: publish v5.54.0chore: fix npm tag publishing for v6 branchfix(typescript-estree): check for relative/root paths in printing file path errors (#6491)chore: hardcode v6 branch name in v6 canary publish (#6512)chore: increase wait-for-netlify max_timeout to 5 minschore(website): correct crash when switching to dark/light mode in playground (#6496)chore(deps): update nx to v15.7.2 (#6507)chore(deps): update probablyup/wait-for-netlify-action action to v3.4.0 (#6502)fix(website): corect playground build issue (#6506)feat(eslint-plugin): [promise-function-async] check for promises in implicit return types (#6330)chore: fix ci token (#6503)chore: publish v5.53.0chore: use read-only token for nx cloud in source control (#6501)chore: run website tests against netlify deployment (#6212)chore(deps): update nx to v15.7.1 (#6482)chore(deps): update dependency lerna to v6.5.1 (#6480)feat(typescript-estree): expose a wrapper cache clearing function for advanced usecases (#6476)feat(eslint-plugin): [consistent-generic-constructors] handle default parameters (#6484)feat(eslint-plugin): [no-mixed-enums] add rule (#6102)docs(website): fix typed rules heading link in custom rule docs (#6460)docs(eslint-plugin): explicit-function-return-type: missing allowFunctionsWithoutTypeParameters sections (#6475)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