|
1 | 1 | # CodeQL CLI changelog |
2 | 2 |
|
| 3 | +## Release 2.5.0 (2021-03-29) |
| 4 | + |
| 5 | +- The bundled extractors are updated to match the versions currently |
| 6 | + used on LGTM.com. These are newer than the last release (1.27) of |
| 7 | + LGTM Enterprise. If you plan to upload databases to an LGTM |
| 8 | + Enterprise 1.27 instance, you need to create them with release |
| 9 | + 2.4.6. |
| 10 | + |
| 11 | +### Potentially breaking changes |
| 12 | + |
| 13 | +- By default, `codeql test` now performs additional compiler |
| 14 | + checks when extracting test code written in Java. |
| 15 | + Existing Java tests that previously passed may therefore fail due |
| 16 | + to this change, if they do not compile using the `javac` compiler. |
| 17 | + To allow time to migrate existing tests, the new behavior can be |
| 18 | + disabled by setting the environment variable |
| 19 | + `CODEQL_EXTRACTOR_JAVA_FLOW_CHECKS=false`. |
| 20 | + |
| 21 | +### Features added |
| 22 | + |
| 23 | +- Log files that contain output from build processes will now prefix |
| 24 | + it with `[build-stdout]` and `[build-stderr]` instead of `[build]` |
| 25 | + and `[build-err]`. In particular the latter sometimes caused |
| 26 | + confusion. |
| 27 | + |
| 28 | +### QL language improvements |
| 29 | + |
| 30 | +- The QL language now recognizes new `pragma[only_bind_into](...)` and |
| 31 | + `pragma[only_bind_out](...)` annotations on expressions. Advanced users |
| 32 | + may use these annotations to provide hints to the compiler to influence |
| 33 | + binding behavior and thus indirectly performance. |
| 34 | + |
3 | 35 | ## Release 2.4.6 (2021-03-19) |
4 | 36 |
|
5 | 37 | This release corresponds to release 1.27.x of LGTM Enterprise, and |
|
0 commit comments