|
16 | 16 | checklist for a CLI release, you can edit here. But then |
17 | 17 | you know what to do). |
18 | 18 | --> |
| 19 | +## Release 2.8.1 (2022-02-15) |
| 20 | +- The bundled extractors are updated to match the versions currently |
| 21 | + used on LGTM.com. These are newer than the last release (1.29) of |
| 22 | + LGTM Enterprise. If you plan to upload databases to an LGTM |
| 23 | + Enterprise 1.29 instance, you need to create them with release |
| 24 | + 2.6.3. |
| 25 | + |
| 26 | +### New Features |
| 27 | + |
| 28 | +- Commands that find or run queries now allow you to refer to queries within a named CodeQL |
| 29 | + pack. For example: |
| 30 | + |
| 31 | + ```sh |
| 32 | + # Analyze a database using all queries in the experimental/Security folder within the codeql/cpp-queries |
| 33 | + # CodeQL query pack. |
| 34 | + codeql database analyze --format=sarif-latest --output=results <db> \ |
| 35 | + codeql/cpp-queries:experimental/Security |
| 36 | + |
| 37 | + # Analyse using only the RedundantNullCheckParam.ql query in the codeql/cpp-queries CodeQL query pack. |
| 38 | + codeql database analyze --format=sarif-latest --output=results <db> \ |
| 39 | + 'codeql/cpp-queries:experimental/Likely Bugs/RedundantNullCheckParam.ql' |
| 40 | + |
| 41 | + # Analyse using the cpp-security-and-quality.qls query suite in the codeql/cpp-queries CodeQL query pack. |
| 42 | + codeql database analyze --format=sarif-latest --output=results <db> \ |
| 43 | + 'codeql/cpp-queries:codeql-suites/cpp-security-and-quality.qls' |
| 44 | + |
| 45 | + # Analyse using the cpp-security-and-quality.qls query suite from a version of the codeql/cpp-queries pack |
| 46 | + # that is >= 0.0.3 and < 0.1.0 (the highest compatible version will be chosen). |
| 47 | + # All valid semver ranges are allowed. See https://docs.npmjs.com/cli/v6/using-npm/semver#ranges |
| 48 | + codeql database analyze --format=sarif-latest --output=results <db> \ |
| 49 | + 'codeql/cpp-queries@~0.0.3:codeql-suites/cpp-security-and-quality.qls' |
| 50 | + ``` |
| 51 | + |
| 52 | + The complete way to specify a set of queries is in the form `scope/name@range:path`, where: |
| 53 | + |
| 54 | + - `scope/name` is the qualified name of a CodeQL pack. |
| 55 | + - `range` is a [semver range](https://docs.npmjs.com/cli/v6/using-npm/semver#ranges). |
| 56 | + - `path` is a file system path |
| 57 | + |
| 58 | + If a `scope/name` is specified, the `range` and `path` are optional. A missing `range` |
| 59 | + implies the latest version of the specified pack. A missing `path` implies the default |
| 60 | + query suite of the specified pack. |
| 61 | + |
| 62 | + The `path` can be one of a `*.ql` query file, a directory containing one or more queries, or a |
| 63 | + `.qls` query suite file. If there is no pack name specified, then a `path` must be provided, and will |
| 64 | + be interpreted relative to the current working directory of the current process. |
| 65 | + |
| 66 | + If a `scope/name` and `path` are specified, then the `path` cannot be absolute. It is considered |
| 67 | + relative to the root of the CodeQL pack. |
| 68 | + |
| 69 | + The relevant commands are: |
| 70 | + - `codeql database analyze` |
| 71 | + - `codeql database run-queries` |
| 72 | + - `codeql execute queries` |
| 73 | + - `codeql resolve queries` |
| 74 | + |
| 75 | +### Bugs fixed |
| 76 | + |
| 77 | +- Fixed a bug that would sometimes lead to query evaluation on |
| 78 | + M1-based Macs to crash with `Did not preallocate enough |
| 79 | + memory` error. |
19 | 80 |
|
20 | 81 | ## Release 2.8.0 (2022-02-04) |
21 | 82 |
|
|
0 commit comments