Skip to content

Commit 2e5c334

Browse files
authored
Update CHANGELOG.md
1 parent 133ec79 commit 2e5c334

File tree

1 file changed

+18
-1
lines changed

1 file changed

+18
-1
lines changed

CHANGELOG.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,23 @@
1717
you know what to do).
1818
-->
1919

20+
## Release 2.19.2 (2024-10-21)
21+
22+
### Potentially breaking changes
23+
24+
- The Python extractor will no longer extract the standard library by default, relying instead on models of the standard library. This should result in significantly faster extraction and analysis times, while the effect on alerts should be minimal. It will for a while be possible to force extraction of the standard library by setting the environment variable `CODEQL_EXTRACTOR_PYTHON_EXTRACT_STDLIB` to `1`.
25+
26+
### Miscellaneous
27+
28+
- The database relation `sourceLocationPrefix` is changed for databases created with
29+
`codeql test run`. Instead of containing the path of the enclosing qlpack, it now
30+
contains the actual path of the test, similar to if one had run `codeql database create`
31+
on the test folder. For example, for a test such as
32+
`<checkout>/cpp/ql/test/query-tests/Security/CWE/CWE-611/XXE.qlref` we now populate
33+
`sourceLocationPrefix` with `<checkout>/cpp/ql/test/query-tests/Security/CWE/CWE-611/`
34+
instead of `<checkout>/cpp/ql/test/`. This change typically impacts calls to
35+
`File.getRelativePath()`, and may as a result change the expected test output.
36+
2037
## Release 2.19.1 (2024-10-04)
2138

2239
### New Features
@@ -515,7 +532,7 @@
515532

516533
- Fixed an issue where CodeQL would sometimes incorrectly report that no files
517534
were scanned when running on Windows.
518-
This affected the human-readable summary produced by `codeql database analyze`
535+
This affected the human-readable summary produced by `codeql database analyze`
519536
and `codeql database interpret-results`, but did not impact the file coverage
520537
information produced in the SARIF output and displayed on the tool status page.
521538
- When analyzing Swift codebases, CodeQL build tracing will now ignore the

0 commit comments

Comments
 (0)