I wanted somewhere to keep track of the breaking changes we should make as part of a 2.0.0 release.

Deprecated Rules:

• (pr feat(eslint-plugin)!: remove deprecated rules #739) remove deprecated rule prefer-interface (replaced by consistent-type-definitions)
• (pr feat(eslint-plugin)!: remove deprecated rules #739) remove deprecated rule no-triple-slash-reference (replaced by triple-slash-reference)
• (pr feat(eslint-plugin)!: add rule consistent-type-assertions #731) remove deprecated rule no-angle-bracket-type-assertion (replaced by consistent-type-assertions)
• (pr feat(eslint-plugin)!: add rule consistent-type-assertions #731) remove deprecated rule no-object-literal-type-assertion (replaced by consistent-type-assertions)

Misc:

• (pr feat: Support eslint@6 #645) Support eslint 6 (drop node 6 support)
• (pr fix(eslint-plugin)!: remove "isTypescriptFile". #594) kill isTypescriptFile checks Make typescript-eslint rules compatible with .vue files #524
• (pr feat(eslint-plugin)!: add rule consistent-type-assertions #731) generalize no-angle-bracket-type-assertion (Rule suggestion: generalize @typescript-eslint/no-angle-bracket-type-assertion #332) and merge in no-object-literal-type-assertion
• (pr feat(typescript-estree)!: throw error on file not in project when project set #760) protection against most common performance pitfall
• (pr fix(eslint-plugin): [explicit-function-return-type] Fix allowExpressions ignoring default exports #831) explicit-function-return-type allowExpressions shouldn't ignore export default () => {}
• rename @typescript-eslint/experimental-utils to @typescript-eslint/utils (feat: Move shared types into their own package #425 (review)) will do in v3
• look into renaming a number of rules Suggestion: standardize against prefixing rule names with "no-" #203 will do with a later major bump..

Recommended stuff:

• reevaluate rule defaults
  • (pr feat(eslint-plugin)!: change recommended config #729) make explicit-function-return-type more relaxed by default, as it's the standard usage ([explicit-function-return-type] Consider allowExpressions=true and allowTypedFunctionExpressions=true as default #493)
  • (feat(eslint-plugin)!: [promise-function-async] make allowAny default true #733) Remove the allowAny option from the promise-function-async rule and make it the default (from comment below)
• (pr feat(eslint-plugin)!: change recommended config #729) update the recommended rule set with new rules (and remove some rules) [recommended] Remove stylistic rules from recommended #651
• (pr feat(eslint-plugin)!: recommended-requiring-type-checking config #846) split the recommended into a base set not requiring type info, and an extension set requiring type info, so people can have a fast experience by default.