Lint fails with "Obsolete custom lint check"

[winterDroid]

Executing Lint with the latest Android Gradle Plugin com.android.tools.build:gradle:3.1.0-alpha08 I'll get a warning in the Lint report namely:

Lint found an issue registry (timber.lint.IssueRegistry) which did not specify the Lint API version it was compiled with.
This means that the lint checks are likely not compatible.
To fix this, make your lint IssueRegistry class contain
override val api: Int = com.android.tools.lint.detector.api.CURRENT_API
or from Java,
@Override public int getApi() { return com.android.tools.lint.detector.api.ApiKt.CURRENT_API; }
Applies to variants: debug
Does not apply to variants: release
Lint can be extended with "custom checks": additional checks implemented by developers and libraries to for example enforce specific API usages required by a library or a company coding style guideline.

The Lint APIs are not yet stable, so these checks may either cause a performance, degradation, or stop working, or provide wrong results.

This warning flags custom lint checks that are found to be using obsolete APIs and will need to be updated to run in the current lint environment.
It may also flag issues found to be using a newer version of the API, meaning that you need to use a newer version of lint (or Android Studio or Gradle plugin etc) to work with these checks.
To suppress this error, use the issue id "ObsoleteLintCustomCheck" as explained in the Suppressing Warnings and Errors section.

[vanniktech]

This is 'expected' since it's somewhat of a breaking change. The solution is to use 26.1.0-alpha08 of the lint dependency, update the necessary bits and release a new version. In the future hopefully this new method will ease this kind of problems.

[jffiorillo]

This is still happening with com.android.tools.build:gradle:3.2.0-alpha14