Henry Mercer

The KR is 25%. I think we should spend some time optimizing the new features to keep us within this performance budget.

I don't think Python 2 is preinstalled in the `ubuntu-22.04` virtual environment. Would it be reasonable to add the combination of `python_version: 2` and `os: ubuntu-22.04` to the `exclude` listing...

Another way to test this might be adding a step that calls `actions/setup-python` with `python-version: 2`, that is only executed when `os == ubuntu-22.04` and `python_version == 2`?

Taking this out of draft since that reruns the PR checks.

https://github.com/github/codeql/pull/10613 will fix the PR check.

Superseded by https://github.com/github/codeql/pull/10781.

Moving back to draft as there's some more work here to send telemetry about the set of languages we tried to autobuild and the language that failed, if relevant.

Closing this in favour of using build modes and having `database trace-command --use-build-mode` determine how to extract the code.

That's right — currently we bring all the latest features from v3 into v2 (apart from Node 20 support), and to do that we have a backport PR like this...

It's not currently documented, so I'm happy with a separate PR if you prefer!