|
17 | 17 | you know what to do). |
18 | 18 | --> |
19 | 19 |
|
| 20 | +## Release 2.27.2 (2026-10-07) |
| 21 | + |
| 22 | +### Improvements |
| 23 | + |
| 24 | +- Error and warning messages printed to standard error are now labelled with an |
| 25 | + `ERROR: ` or `WARNING: ` prefix. Previously only diagnostics carried such a |
| 26 | + label, so the severity of other messages was not apparent in plain-text |
| 27 | + output. Structured output is unaffected: log files, SARIF, and stored |
| 28 | + diagnostics continue to record severity without the prefix. |
| 29 | +- The `codeql query compile` command now accepts the `--dil-constants` |
| 30 | + flag. When specified along with `--dump-dil`, the emitted DIL |
| 31 | + will include the values of predicates that have been optimized into |
| 32 | + constant tuple sets. Otherwise, these constants are omitted. This flag |
| 33 | + also enables pretty-printing of constant tuple sets for higher-level |
| 34 | + commands that involve query compilation. |
| 35 | + |
| 36 | +### Bug Fixes |
| 37 | + |
| 38 | +- Fixed a crash in `codeql resolve queries` (and other commands that |
| 39 | + resolve query suites) that reported a fatal internal error when a suite |
| 40 | + entry's `qlpack:` or `from:` value was not a valid QL pack name. Such |
| 41 | + input now produces a clear, user-facing error instead. |
| 42 | +- Fixed a bug in the handling of YAML data extensions that would quietly accept integers outside of |
| 43 | + the signed 64-bit range, truncating them to smaller values. (Values outside of the signed 32-bit |
| 44 | + range, but inside the signed 64-bit range, were correctly rejected.) Now, all integers outside of |
| 45 | + the signed 32-bit range are rejected and will cause evaluation to fail. |
| 46 | + |
| 47 | +### Miscellaneous |
| 48 | + |
| 49 | +- CLI commands that load data extensions, such as `codeql database run-queries`, |
| 50 | + previously emitted a warning for each file-pattern from the `dataExtensions` |
| 51 | + list of a `qlpack.yml` manifest that failed to match any extension files. |
| 52 | + This check has been relaxed, and will now only emit a warning if none of the |
| 53 | + patterns match any files (i.e. when there is at least one pattern but no |
| 54 | + extensions are found). |
| 55 | + |
20 | 56 | ## Release 2.27.1 (2026-09-22) |
21 | 57 |
|
22 | 58 | ### Miscellaneous |
|
0 commit comments