We haven't released that feature to main yet.

Please use the canary tag on npm:
npm install @typescript-eslint/eslint-plugin@canary

@bradzacher, if it's not released yet, why is it documented in master?

https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/explicit-member-accessibility.md

We don't have a separate release branch, master is our pr target branch because it makes life easier. We release to the main tag on npm every week or two. It's a manual release so it happens when we get to it.

We have CI to automatically run a canary release for every master commit. If you want the bleeding edge always without waiting, just install from the canary tag.
So far we haven't ever had changes between canary and master, so it's safe to use.

Ahh cool, didn't take into account what your release cycle looked like, thanks for the explanation!

@bradzacher Is there a list of the rules that are currently supported in master?

@dlhart - do you mean currently supported against the latest tag on npm or the canary tag on npm?

Because the answer to your question is whatever is in master is what's supported in master......

For the code that's currently released as latest - we generate git tags and release notes on every single latest release. You can use github's tag navigation to see exactly what is supported by a specific version.

The code that's currently released as canary is just whatever is in master.