Next major #1531
Merged
Next major #1531
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
# [28.0.0-next.1](v27.9.0...v28.0.0-next.1) (2024-03-21) ### Features * remove `no-if` rule ([#1528](#1528)) ([f976fc8](f976fc8)) ### BREAKING CHANGES * removed `no-if` in favor of `no-conditional-in-test`
BREAKING CHANGE: dropped support for Node v14
# [28.0.0-next.2](v28.0.0-next.1...v28.0.0-next.2) (2024-03-21) ### Features * drop support for Node v14 ([#1527](#1527)) ([df5e580](df5e580)) ### BREAKING CHANGES * dropped support for Node v14
* feat: upgrade to `@typescript-eslint/utils` v6 * chore: remove invalid module declarations * fix: update `docs` meta property on rules * chore: cast `context.settings` for now * refactor: update deprecated method calls * fix: update types for `JSONSchema4` * test(unbound-method): update cases and structure * test(unbound-method): use `TSESLint.RuleTester` * test(unbound-method): include filename for invalid cases * test(unbound-method): don't run broken test when using `@typescript-eslint` v5 * fix: address deprecation warning
# [28.0.0-next.3](v28.0.0-next.2...v28.0.0-next.3) (2024-03-22) ### Features * upgrade `@typescript-eslint/utils` to v6 ([#1508](#1508)) ([dc6e8cd](dc6e8cd))
BREAKING CHANGE: dropped support for `@typescript-eslint/eslint-plugin` v5
# [28.0.0-next.4](v28.0.0-next.3...v28.0.0-next.4) (2024-03-23) ### Features * drop support for `@typescript-eslint/eslint-plugin` v5 ([#1530](#1530)) ([150e355](150e355)) ### BREAKING CHANGES * dropped support for `@typescript-eslint/eslint-plugin` v5
github-actions
bot
added
rule: no-mocks-import
rule: no-conditional-expect
rule: no-alias-methods
rule: no-restricted-jest-methods
rule: no-jasmine-globals
rule: no-done-callback
rule: prefer-to-be
rule: prefer-each
rule: no-test-prefixes
rule: no-identical-title
rule: expect-expect
rule: no-large-snapshots
rule: prefer-hooks-on-top
rule: prefer-lowercase-title
rule: no-standalone-expect
rule: no-focused-tests
rule: no-confusing-set-timeout
rule: no-duplicate-hooks
rule: prefer-called-with
rule: no-conditional-in-test
labels
BREAKING CHANGE: removed unneeded `snapshot` processor and `flat/snapshot` config
# [28.0.0-next.5](v28.0.0-next.4...v28.0.0-next.5) (2024-03-27) ### Features * remove `snapshot` processor and `flat/snapshot` config ([#1532](#1532)) ([98087f9](98087f9)) ### BREAKING CHANGES * removed unneeded `snapshot` processor and `flat/snapshot` config
…1540) * test(prefer-comparison-matcher): update test names * test(prefer-comparison-matcher): deduplicate examples
…9 compatibility (#1542)
# [28.0.0-next.6](v28.0.0-next.5...v28.0.0-next.6) (2024-03-29) ### Bug Fixes * **no-large-snapshots:** avoid `instanceof RegExp` check for ESLint v9 compatibility ([#1542](#1542)) ([af4a9c9](af4a9c9))
|
I think this is good to go - there's a few fixes that don't require a new major but I didn't land them in |
* ci: run against next ESLint * test: make util * test: use a class * test: use a class (2) * test: improve compat class * refactor: make `flatCompat` util private * test: get `linter#verify` cases passing * ci: skip lint project on eslint v9 * test: ignore coverage in util class * chore: move Jest config into dedicated file * ci: handle skipping linting in Jest config * test: skip `unbound-method` when using `@typescript-eslint` v6 * ci: skip ESLint v9 on Node v16 * refactor: import `Config` from `jest` directly * refactor: address `@ts-expect-error`s * refactor: use a constant instead of a function
SimenB
approved these changes
Apr 6, 2024
BREAKING CHANGE: Node v19 is no longer supported
|
🎉 This PR is included in version 28.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
Incredible work on this release @G-Rath, thank you so much! |
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.
The only major changes left I can think of are changes to config and rule defaults (of which I can't think of any we actually wanted to do?) and maybe changing our snapshot processor which I'm not actually sure we need anymore? (Will discuss on #292)
Resolves #292