Michael B. Gale

@brian-welsh I have responded in the issue you created/linked.

Hi @ulgens, Thanks -- we are aware and in the process of updating the Default Setup workflow to use `v4`. Obviously this will be done in good time before `v3`...

> If it's too early even for GitHub to use v4, why is there even a deprecation warning? In general, the purpose of a deprecation message is to give as...

@henrymercer I rebased to resolve merge conflicts and added https://github.com/github/codeql-action/pull/3006/commits/483613152e5f7147dbb891be42c168136269ccc2 since the init logic in `uploadSpecifiedFiles` shouldn't be needed anymore. It would probably be nicer if we split up that...

Not a bad idea. It would probably mean throwing most of the changes in this PR out, but it would be a simpler overall change and not require us to...

`codeql pack download [name]` will download the pack to the default location. Generally speaking there are two scenarios: 1. You install a CLI bundle, which ships with all the default...

No. Generally, the intent is that you publish your pack and then install it with `codeql pack download`. If you only have the pack locally, then you should be able...

Hi @wsugarman 👋🏻 > Is that truly the issue, [..] Broadly, yes, but also see my response over in https://github.com/github/codeql-action/issues/3207#issuecomment-3518063679 > [..] and if so is there a timeline for...

Hi @intrigus-lgtm 👋🏻 The way that Rust support for CodeQL is implemented is a bit different from other languages, which means that types aren't extracted and so cannot easily be...

Hi @drank40 👋🏻 Do you have any custom queries that you think should work, but don't? Or do you expect some of the default queries to find results that they...