|
4 | 4 |
|
5 | 5 | ### Changed: faster local scan setup for large repositories |
6 | 6 |
|
7 | | -- Replaced repeated per-pattern recursive manifest globs with one streaming |
8 | | - filesystem walk per scan root. Excluded directories and `.git` are pruned |
9 | | - before descent, reducing filesystem metadata work without building a |
10 | | - repository-sized in-memory file index. |
11 | | -- Removed the unconditional `git fetch --all` from CLI initialization. Pull |
12 | | - request scans now use local refs first and fetch only a required base or head |
13 | | - ref when the checkout does not contain enough history. |
14 | | -- Added native Buildkite commit, branch, pull-request range, and GitHub SCM |
15 | | - configuration fallbacks so Buildkite jobs no longer need GitHub |
16 | | - Actions-shaped environment-variable shims. |
17 | | -- Added INFO-level timings for CLI run registration, organization setup, Git |
18 | | - initialization and fetches, changed-file detection, supported-pattern lookup, |
19 | | - and manifest discovery. |
20 | | -- Supported manifest patterns are cached for each CLI invocation once the API |
21 | | - returns them, so a transient lookup failure no longer keeps the run on the |
22 | | - smaller local fallback pattern set. Manifest results from `--sub-path` routing |
23 | | - are reused during scan creation. |
| 7 | +- Manifest discovery now uses one filesystem walk per scan root and prunes |
| 8 | + excluded directories before descent. |
| 9 | +- Pull request scans use local Git refs first and fetch only missing history. |
| 10 | + Buildkite pull request metadata is now supported directly. |
| 11 | +- Supported manifest patterns are cached per invocation, and discovered |
| 12 | + manifests are reused during scan creation. |
| 13 | +- Added timings for initialization, Git operations, changed-file detection, |
| 14 | + pattern lookup, and manifest discovery. |
24 | 15 |
|
25 | 16 | ### Changed: scan comparisons no longer fetch unused artifacts |
26 | 17 |
|
27 | | -- Scan comparisons now ask the API to omit unchanged artifacts unless an enabled |
28 | | - output actually reads them (`--strict-blocking`, `--enable-gitlab-security`, |
29 | | - `--generate-license`, or `--legal-format fossa`). Cached comparison responses |
30 | | - embed every unchanged artifact at roughly 1 KB each, so on a large dependency |
31 | | - tree this was most of the response — over 10 MB for a tree of ~10k unchanged |
32 | | - packages — downloaded and parsed on every pull request even when nothing read |
33 | | - it. Behavior is unchanged for any run that uses those outputs. |
34 | | - |
35 | | -### Changed: scan comparison timing is easier to attribute |
36 | | - |
37 | | -- Lowered the diff-scan poll ceiling from 30s to 10s. A finished comparison is no |
38 | | - longer left unobserved for up to half a minute, which matters when the CLI runs |
39 | | - inside a CI step with a per-step time budget. |
40 | | -- Diff scans now log their ID, poll count, and the wait before the final poll, so |
41 | | - a CI log distinguishes backend comparison time from time spent between polls. |
| 18 | +- Scan comparisons omit unchanged artifacts unless an enabled output needs them. |
| 19 | +- Diff scans poll more frequently and log identifiers and timing details for |
| 20 | + easier troubleshooting. |
42 | 21 | - Documented the `diff-scans:create`, `diff-scans:list` and `full-scans:list` |
43 | | - token scopes. Without them the comparison silently falls back to the older |
44 | | - streaming path. |
| 22 | + token scopes required by the optimized comparison path. |
45 | 23 |
|
46 | 24 | ## 2.6.5 |
47 | 25 |
|
|
0 commit comments