Upgrade @angular-eslint/*

[vitaliibendyk]

BREAKING CHANGE:
Requires angular 19.

[michaelwittwer]

The commit message is a bit misleading, since this change has not directly todo with angular@19 but instead with @angular-eslint/* packages, which then use angular@19 under the hood, but let's keep it like that
@michaelwittwer I based my commit message on your analog

[michaelwittwer]

if there is no explicit reason on why 19.0.0 & 19.0.1 are not allowed, I would just use ^19.0.0 as peerDep definition.

[michaelwittwer]

use the latest versions here and next line

[michaelwittwer]

@vitaliibendyk did you check the CHANGELOG and Announcing Typescript EsLint 8 to make sure there are no additional changes necessary?

[michaelwittwer]

@vitaliibendyk every new version of @angular-eslint brings changes to which rules are enabled, make sure to test this version in an existing project to know if we need to update our rules configuration.

[michaelwittwer]

@vitaliibendyk please also update the @angular-esling/* packages in our eslint-plugin-rules package.
@michaelwittwer We don't have that

[michaelwittwer]

The commit message is a bit misleading, since this change has not directly todo with angular@19 but instead with @angular-eslint/* packages, which then use angular@19 under the hood, but let's keep it like that @michaelwittwer I based my commit message on your analog

Thanks for pointing it out. In the end it's true, but not the full story. 🙈 As i said, leave it like that.

[michaelwittwer]

@vitaliibendyk please also update the @angular-esling/* packages in our eslint-plugin-rules package. @michaelwittwer We don't have that

You are right. I meant @typescript-eslint/*, since this is probably also a BREAKING CHANGE but only upgrade if it still works with eslint@8