I've pushed a fix for a bug in #1527 that meant we passed a --qlconfig=undefined argument when there was no qlconfig file. I've also merged in main to bring in #1560 which should fix the issues with setup-swift.

Thanks for the fix, @henrymercer. I've confirmed that it works locally. I created a PR against main to fix it there. #1564

I've pushed a fix for a bug in #1527 that meant we passed a --qlconfig=undefined argument

Erm, yes, I’m running into this because the bundle has been updated (compared to the previous run of the action). But there’s no new release; how do I get the builds working again?

Ah well, reverting to an earlier version codeql-bundle-20230105 worked.

Erm, yes, I’m running into this because the bundle has been updated (compared to the previous run of the action). But there’s no new release; how do I get the builds working again?

Hi @mirabilos — this fix was released in version 2.2.6 of the CodeQL Action. Please let us know if you still aren't able to use the latest bundle.

We release the CodeQL Action using git tags, and release CodeQL Action Bundles using GitHub Releases. It looks like the tool you're using is only picking up on the GitHub Releases. We'd recommend configuring your workflow to use the v2 tag (for example uses: github/codeql-action/init@v2). We update this tag with each release.