Add doc describing CLI version marker files
This commit is contained in:
parent
a89ad76881
commit
31c7ce1ce4
3 changed files with 21 additions and 1 deletions
10
lib/setup-codeql.js
generated
10
lib/setup-codeql.js
generated
|
|
@ -65,6 +65,16 @@ function getCodeQLActionRepository(logger) {
|
|||
return util.getRequiredEnvParam("GITHUB_ACTION_REPOSITORY");
|
||||
}
|
||||
exports.getCodeQLActionRepository = getCodeQLActionRepository;
|
||||
/**
|
||||
* CodeQL bundles are currently tagged in the form `codeql-bundle-yyyymmdd`, so it is not possible
|
||||
* to directly find the CodeQL bundle release for a particular CLI version.
|
||||
*
|
||||
* To get around this, we add a `codeql-version-x.y.z.txt` asset to each bundle release that
|
||||
* specifies the CLI version for that bundle release.
|
||||
*
|
||||
* In the medium term, we should migrate to a tagging scheme that allows us to directly find the
|
||||
* CodeQL bundle release for a particular CLI version, for example `codeql-bundle-vx.y.z`.
|
||||
*/
|
||||
async function findCodeQLBundleTagDotcomOnly(cliVersion, logger) {
|
||||
logger.debug(`Trying to find the CodeQL bundle release for CLI version ${cliVersion}.`);
|
||||
const apiClient = api.getApiClient();
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
Loading…
Add table
Add a link
Reference in a new issue