i’ve read the compatibility matrix on github and in fact i’ve tried with the latest Sonarqube 8.8 version.
As you already mentioned, it doesn’t make sense to release a new plugin version compatible with Sonarqube 8.2 when the next LTS version 8.9 is just around the corner.
Also i believe Sonarqube 8.8 is not the problem.
Noticed this bug already from the beginning in 2019 with Sonarqube 7.9, see
and also with subsequent versions of the CNES report plugin.