Update all of typescript-eslint 6.18.0 → 6.18.1 (patch) #74
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 (6.18.0 → 6.18.1) · Repo · Changelog
Release Notes
6.18.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 19 commits:
chore(release): publish 6.18.1
chore: fix test formatting in prefer-readonly.test.ts (#8223)
chore: fix yargs call in release script (#8221)
chore(deps): update dependency tsx to v4.7.0 (#8162)
fix(eslint-plugin): [switch-exhaustiveness-check] fix new allowDefaultCaseForExhaustiveSwitch option (#8176)
fix(eslint-plugin): [prefer-readonly] support modifiers of unions and intersections (#8169)
fix(eslint-plugin): [no-unnecessary-condition] improve checking optional callee (#8178)
fix(eslint-plugin): [no-non-null-assertion] provide valid fix when member access is on next line (#8185)
chore(typescript-estree): remove unnecessary old snapshots (#8198)
chore: prevent a11y-alt-text-bot workflow when author is a bot (#8212)
docs: document allowAutomaticSingleRunInference (#8138)
chore: enable eslint-plugin-jsdoc internally (#8145)
chore: rename release.ts to release.mts (#8204)
chore: enable no-dynamic-delete internally (#7954)
fix(utils): improve error message on typed rule with invalid parser (#8146)
fix(typescript-estree): only create project service from env setting if project is enabled (#8136)
fix(typescript-estree): fix invalid parsing error when use update expression on non-null assertion (#8202)
chore: release script updates (#8203)
chore: update lockfile after release
✳️ @typescript-eslint/parser (6.18.0 → 6.18.1) · Repo · Changelog
Release Notes
6.18.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 19 commits:
chore(release): publish 6.18.1
chore: fix test formatting in prefer-readonly.test.ts (#8223)
chore: fix yargs call in release script (#8221)
chore(deps): update dependency tsx to v4.7.0 (#8162)
fix(eslint-plugin): [switch-exhaustiveness-check] fix new allowDefaultCaseForExhaustiveSwitch option (#8176)
fix(eslint-plugin): [prefer-readonly] support modifiers of unions and intersections (#8169)
fix(eslint-plugin): [no-unnecessary-condition] improve checking optional callee (#8178)
fix(eslint-plugin): [no-non-null-assertion] provide valid fix when member access is on next line (#8185)
chore(typescript-estree): remove unnecessary old snapshots (#8198)
chore: prevent a11y-alt-text-bot workflow when author is a bot (#8212)
docs: document allowAutomaticSingleRunInference (#8138)
chore: enable eslint-plugin-jsdoc internally (#8145)
chore: rename release.ts to release.mts (#8204)
chore: enable no-dynamic-delete internally (#7954)
fix(utils): improve error message on typed rule with invalid parser (#8146)
fix(typescript-estree): only create project service from env setting if project is enabled (#8136)
fix(typescript-estree): fix invalid parsing error when use update expression on non-null assertion (#8202)
chore: release script updates (#8203)
chore: update lockfile after release
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