|
17 | 17 | you know what to do).
|
18 | 18 | -->
|
19 | 19 |
|
| 20 | +## Release 2.19.3 (2024-11-07) |
| 21 | + |
| 22 | +### Bugs fixed |
| 23 | + |
| 24 | +- Fixed a bug where using `codeql database import` to combine multiple non-empty |
| 25 | + databases may produce a corrupted database. (The bug does not affect using |
| 26 | + `codeql database finalize --additional-dbs` to combine multiple databases.) |
| 27 | + |
| 28 | +- Fixed a bug where uses of a `QlBuiltins::ExtensionId` variable that was not |
| 29 | + bound to a value could be incorrectly accepted in some cases. In many cases, |
| 30 | + this would result in a crash. |
| 31 | + |
| 32 | +- CodeQL would sometimes refuse to run with more than around 1,500 GB of RAM |
| 33 | + available, complaining that having so much memory was "unrealistic". The |
| 34 | + amount of memory CodeQL is able to make any meaningful use of still tops out |
| 35 | + at about that value, but it will now gracefully accept that so large |
| 36 | + computers do in fact exist. |
| 37 | + |
| 38 | +- Fixed a bug in command-line parsing where a misspelled option could sometimes |
| 39 | + be misinterpreted as, e.g., the name of a query to run. Now every command-line |
| 40 | + argument that begins with a dash is assumed to be intended as an option |
| 41 | + (unless it comes after the `--` separator), and an appropriate error is |
| 42 | + emitted if that is not a recognized one. |
| 43 | + |
| 44 | + The build command in `codeql database trace-command` is exempted from this for |
| 45 | + historical reasons, but we strongly recommend putting a `--` before the entire |
| 46 | + build command there, in case a future `codeql` version starts recognizing |
| 47 | + options that you intended to be part of the build command. |
| 48 | + |
| 49 | +### Miscellaneous |
| 50 | + |
| 51 | +- The CodeQL Bundle is now available as an artifact that is compressed using |
| 52 | + [Zstandard](https://en.wikipedia.org/wiki/Zstd). This artifact is |
| 53 | + smaller and faster to decompress than the original, gzip-compressed bundle. The CodeQL bundle |
| 54 | + is a tar archive containing tools, scripts, and various CodeQL-specific files. |
| 55 | + |
| 56 | + If you are currently using the CodeQL Bundle, you may want to consider switching to the |
| 57 | + Zstandard variant of the bundle. You can download the new form of the CodeQL Bundle from the |
| 58 | + [codeql-action releases page](https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.19.3) |
| 59 | + by selecting the appropriate bundle with the `.zst` extension. The gzip-compressed bundles will |
| 60 | + continue to be available for backwards compatibility. |
| 61 | + |
20 | 62 | ## Release 2.19.2 (2024-10-21)
|
21 | 63 |
|
22 | 64 | ### Potentially breaking changes
|
|
536 | 578 |
|
537 | 579 | - Fixed an issue where CodeQL would sometimes incorrectly report that no files
|
538 | 580 | were scanned when running on Windows.
|
539 |
| - This affected the human-readable summary produced by `codeql database analyze` |
| 581 | + This affected the human-readable summary produced by `codeql database analyze` |
540 | 582 | and `codeql database interpret-results`, but did not impact the file coverage
|
541 | 583 | information produced in the SARIF output and displayed on the tool status page.
|
542 | 584 | - When analyzing Swift codebases, CodeQL build tracing will now ignore the
|
|
0 commit comments