|
17 | 17 | you know what to do). |
18 | 18 | --> |
19 | 19 |
|
| 20 | +## Release 2.17.0 (2024-04-04) |
| 21 | + |
| 22 | +### Deprecations |
| 23 | + |
| 24 | +- The `--[no-]analysis-summary-v2` and `--[no-]new-analysis-summary` options |
| 25 | + that were used to enable (or disable) improved summary information printed at |
| 26 | + the end of a `codeql database analyze` invocation are no longer supported. |
| 27 | + Improved summary information is now enabled for all invocations. |
| 28 | +- Support for overwriting default CodeQL SARIF run properties using the |
| 29 | + `--sarif-run-property` command line option has been removed. This removes the |
| 30 | + ability to overwrite the `semmle.formatSpecifier`, `metricResults`, and |
| 31 | + `codeqlConfigSummary` properties in the SARIF run file. |
| 32 | + |
| 33 | +### Improvements |
| 34 | + |
| 35 | +- TRAP import (a part of `codeql database create` and `codeql database finalize`) |
| 36 | + now performs better in low-memory situations. (Put another way, it now needs |
| 37 | + less RAM to achieve the same performance as before.) |
| 38 | + |
| 39 | +- The worst-case performance of transitive closure computation (using |
| 40 | + the `+` or `*` postfix operators or the `fastTC` higher-order |
| 41 | + primitive in QL) has been greatly improved. |
| 42 | + |
| 43 | +### Miscellaneous |
| 44 | + |
| 45 | +- The build of Eclipse Temurin OpenJDK that is used to run the CodeQL |
| 46 | + CLI has been updated to version 21.0.2. |
| 47 | + |
20 | 48 | ## Release 2.16.6 (2024-03-26) |
21 | 49 |
|
22 | 50 | ### Bugs fixed |
|
75 | 103 |
|
76 | 104 | ### New Features |
77 | 105 |
|
78 | | -- A new extractor option has been added to the Python extractor. |
79 | | - Pass one of `--extractor-option python_executable_name=py` |
80 | | - or `--extractor-option python_executable_name=python` |
81 | | - or `--extractor-option python_executable_name=python3` |
82 | | - to `codeql database create` (or `codeql database trace-command` or, |
83 | | - for indirect tracing, `codeql database init`) to override the default |
84 | | - Python executable search and selection behavior of the Python |
85 | | - extractor. For example, on Windows machines, the Python extractor |
86 | | - will expect to find `py.exe` on the system `PATH` by default. |
87 | | - Setting this extractor option or environment variable allows |
88 | | - overriding this behavior to look for a different name. |
| 106 | +- A new extractor option has been added to the Python extractor: |
| 107 | + `python_executable_name`. You can use this option to override the default |
| 108 | + process the extractor uses to find and select a Python executable. Pass one of |
| 109 | + `--extractor-option python_executable_name=py` or `--extractor-option |
| 110 | + python_executable_name=python` or `--extractor-option |
| 111 | + python_executable_name=python3` to commands that run the extractor, for |
| 112 | + example: `codeql database create`. |
| 113 | + |
| 114 | + On Windows machines, the Python extractor will expect to find `py.exe` on the |
| 115 | + system `PATH` by default. If the Python executable has a different name, you |
| 116 | + can set the new extractor option to override this value and look for |
| 117 | + `python.exe` or `python3.exe`. |
89 | 118 |
|
90 | | - More detail can be found in [the extractor option documentation](https://docs.github.com/en/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/extractor-options). |
| 119 | + For more information about using the extractor option with the CodeQL CLI, see |
| 120 | + [Extractor |
| 121 | + options](https://docs.github.com/en/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/extractor-options). |
91 | 122 |
|
92 | 123 | ### Bugs fixed |
93 | 124 |
|
|
177 | 208 |
|
178 | 209 | - Fixed an issue where CodeQL would sometimes incorrectly report that no files |
179 | 210 | were scanned when running on Windows. |
180 | | - This affected the human-readable summary produced by `codeql database analyze` |
| 211 | + This affected the human-readable summary produced by `codeql database analyze` |
181 | 212 | and `codeql database interpret-results`, but did not impact the file coverage |
182 | 213 | information produced in the SARIF output and displayed on the tool status page. |
183 | 214 | - When analyzing Swift codebases, CodeQL build tracing will now ignore the |
|
0 commit comments