Gareth Jones

I assume you're meaning TypeScripts version of `private`, in which case what the rule has done is valid as the code will still run correctly, and there's no way of...

> Is there an existing rule that can catch this? No there isn't - we actually recommend using promises instead of `done`, though I can't decide if that would help...

@MichaelDeBoey @Belco90 someone with access to the NPM package will need to setup the trusted publisher, similar to [this](https://github.com/jest-community/eslint-plugin-jest/pull/1832#issuecomment-3433827416). Once that is done, I'll mark this as ready-for-review

I personally am not particularly motivated to have this as I've never been convinced that `no-magic-numbers` leads to more maintainable code and I feel like that is especially true in...

Note that _only_ v5.6.1 was compromised, so v4 versions of Chalk are not vulnerable and don't need updating

@ljharb I'm probably going to knock off soon - would you mind having a look over both the changes and CI, and leave me some pointers for the coming days?...

Yup part of this includes switching to a custom rule tester that converts the tests from eslintrc to flat config if they're running on v9, which is what we've been...

If you're meaning the context helper stuff, yeah I'm happy to pull them out I just figured you'd have asked them to be tested against ESLint v9 to prove they...

Right well they're already good for cherry-picking - you want to pick from e31fe5c8...543e3786 (sans f0853cb6 once #2997 is landed), and away you go. I think you can have the...

@ljharb `RuleTester` does not support eslintrc in v9 - the env variable is only used by the CLI