-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kotlin: "CodeQL currently supports versions below 2.1.10" #18596
Comments
Never mind, seems like our TI just uses an outdated version (AFAIK 2.1.10 should work according to https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/ it's "2.1.2x") Update: They use indeed the newest version, now I am confused why this breaks Sonar. |
We are running into the same issue and we are using the most recent version of the CodeQL GitHub action (v3.28.5). |
This issue started occurring for us when we upgraded from Kotlin 2.1.0 to 2.1.10. As said the CodeQL GitHub action we use is that latest (v3.28.5). Part of the stacktrace from our GitHub CodeQL workflow:
|
Hi @edgarvonk,
|
Hi @rvermeulen, we run into the same issue. We use CodeQL with the latest GitHub CodeQL Action:
That uses CodeQL version 2.20.3: |
Hi @rvermeulen , same as above. Our CodeQL GitHub workflow uses CodeQL version 2.20.3 looking at the logs:
ps: you mean Kotlin 2.1.10 I think? |
This is our GitHub CodeQL workflow step just to be complete:
|
PS: a new CodeQL GitHub Action just came out (v3.28.6). I don't see anything related to this issue in the commit log however. |
I did mean 2.1.10 |
I have corrected my previous statement around support for |
@rvermeulen: So this will break again for Kotlin 2.1.20 and 2.1.30? Why is support even restricted on patch (!) level? This could even prevent users from installing security fixes for the compiler. And why will it break the process alltogether, even if there isn't any sort of incompatibility? Wouldn't warning not be enough until this is sorted out? Feels like a ticking timebomb each time.. |
Good question. I've proposed here already to relax the version check in that regard. |
@sschuberth @spyro2000 @rvermeulen i've created a new issue for this #18624 |
@spyro2000 good question. Let me inquire why we have such a restriction on the patch level. |
There was a new release of the CodeQL Action that adds support for Kotlin |
Thank you @rvermeulen, will this break again for Kotlin 2.1.20, 2.1.30 etc? |
Sorry for the failures; this should be fixed now. Please let us know if you're still seeing problems.
In general, if the 10s digit changes then APIs that we use might have changed, so just warning isn't an option. We aim to have support for new versions out before the Kotlin release is made, but unfortunately we didn't quite make it this time. |
Is there any update planed on this? Why is 2.1.9 ok, but 2.1.10 is breaking...?
For whatever reason, the Kotlin team decided to go from 2.1 directly to 2.1.10. Next one will bei 2.1.20. Each incremental step will break CodeQL again, correct?
The text was updated successfully, but these errors were encountered: