Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Consider testing CodeQL also against Kotlin EA versions

Open
#22,219 2 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, kotlin
Domain
ci-cd, testing-qa

Research direction

Start by reviewing the reported CodeQL issues and the Kotlin early-access version documentation, then inspect the repository's existing GitHub Actions workflows for Kotlin version testing. Determine whether a matrix can test current CodeQL against Kotlin EAP releases and define how failures should surface. Done means the approach is documented or implemented with maintainable coverage for EAP versions.

Written by the indexing model from the issue text.

Description

question

Description of the issue

For some time now, all projects using Kotlin and CodeQL face the following situation:

  1. A new Kotlin version is released
  2. Dependabot, Renovate, or equivalent creates a PR to upgrade Kotlin
  3. The PR fails as CodeQL doesn't support the new version yet
  4. After some weeks, a CodeQL release is out for that version, but a new Kotlin version is also released briefly after, which basically restarts the process from step 1

The reported cases since last October:

Just by looking at the timeline of some of these issues, it should be visible how many public projects keep the Kotlin upgrade on hold due to the CodeQL compatibility.

Would you consider testing the current CodeQL version against the Kotlin early-access versions?

I understand testing against EA versions won't necessarily mean anticipating the necessary changes, but I wonder if something relatively cheap could be achieved with a GitHub Actions matrix to at least bring awareness to the process.

Dominant language
CodeQL
Stars
10.1k
Forks
2.1k
Avg merge
2d 10h
Merged PRs (30d)
134

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/codeql

All issues in github/codeql

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.