you broke codeql

[mcandre]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Code quality

Discussion Details

CodeQL stopped working. Instead of scanning my Go code, CodeQL triggers nasty internal errors.

This job attempted to run with improved incremental analysis but it did not complete successfully.

We were unable to automatically build your code. Please replace the call to the autobuild action with your custom build steps.

The breakage may be related to Go v1.27. Various Go tools, such as linters and parser libraries, require updates to account for programming language syntax changes.

I'm using the default CodeQL configuration.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[cartergray234]

This is likely a Go 1.27 compatibility issue. Try pinning Go to the previous version and rerun CodeQL; if that works, the issue is with tooling support rather than your configuration.

[mcandre]

My projects depend on Go 1.27. I can't use earlier versions. Go 1.26 and below have known bugs regarding error handling logic for the govulncheck SAST tool's CLI syntax validation.

[mcandre]

Microsoft is a trillion dollar company. Surely they can afford to hire more DevOps to futureproof CodeQL.

[jketema]

Hi @mcandre.

We actively block analysis of new major Go versions when CodeQL doesn't support that version yet, as analysis might silently fail, which is even less user friendly than the current behavior. Once a new major Go version is released we strive to support it as soon as possible.

In the case of Go 1.27, support went into our tree yesterday, and it will land in CodeQL 2.26.3, which is scheduled to be released next week. If you really need support now, you could try the latest nightly from https://github.com/dsp-testing/codeql-cli-nightlies/releases. Note that we do not offer support on our nightlies.

[radutopala]

This got fixed:

• CodeQL Action v4.37.9 (2026-08-26) moved the default bundle to CLI 2.26.4 — see src/defaults.json@v4.37.9 ("cliVersion": "2.26.4").
• The Go extractor's supported-version ceiling was raised from 1.26 to 1.27 exactly between the two CLI releases: build-environment.go@codeql-cli/v2.26.3 has maxGoVersion = util.NewSemVer("1.26"), while @codeql-cli/v2.26.4 has "1.27".

[jketema]

Correct. This is now been rolled out.