|
1 | 1 | # Changelog |
2 | 2 |
|
3 | | -## 2.7.0 |
| 3 | +## 2.8.0 |
4 | 4 |
|
5 | 5 | ### Changed: improve monorepo scan diagnostics and guidance |
6 | 6 |
|
|
14 | 14 | - Full-scan and streamed-diff API failures now use the configured infrastructure |
15 | 15 | error exit code instead of the security-finding exit code. |
16 | 16 |
|
| 17 | +## 2.7.1 |
| 18 | + |
| 19 | +### Changed: bump pinned @coana-tech/cli to 15.10.36 |
| 20 | + |
| 21 | +- Bumped the pinned reachability engine (`@coana-tech/cli`) from `15.10.32` to |
| 22 | + `15.10.36`. See the [Coana changelogs](https://docs.coana.tech/changelogs) for |
| 23 | + engine changes. |
| 24 | + |
| 25 | +## 2.7.0 |
| 26 | + |
| 27 | +### Fixed: unreadable reachability facts no longer report a blocking package |
| 28 | + |
| 29 | +- Scans with no supported manifest files uploaded a zero-byte `.socket.facts.json` |
| 30 | + placeholder. The API cannot parse that, and answers by adding a |
| 31 | + `generic/invalid-socket-facts@1.0.0` artifact to the scan, which the CLI then reported |
| 32 | + as a new blocking package with no manifest file and no introducing dependency — |
| 33 | + failing the run and, on pull requests, leaving a security comment that could not be |
| 34 | + acted on. The placeholder is now an empty but well-formed facts document. |
| 35 | +- When the API does report `generic/invalid-socket-facts` (a diagnostic for a facts file |
| 36 | + it could not parse, not a real dependency), the CLI now excludes it from scan results |
| 37 | + and logs a warning instead. It no longer blocks a run, appears in reports, or triggers |
| 38 | + a pull request comment. |
| 39 | +- Each placeholder is written to its own temporary directory. Two CLI runs sharing a |
| 40 | + temporary directory previously used the same path and could remove each other's |
| 41 | + placeholder mid-upload. |
| 42 | + |
| 43 | +### Fixed: pull request comments no longer show orphaned tags or an empty table |
| 44 | + |
| 45 | +- Optional sections that rendered as empty, such as the ignore instructions |
| 46 | + suppressed by `--disable-ignore`, left a whitespace-only line in the alerts |
| 47 | + table. That line closed the surrounding HTML block, and the indented |
| 48 | + `</blockquote></details>` tags after it were rendered as a literal code block. |
| 49 | + Generated comment markup now omits blank lines and stays under the indentation |
| 50 | + that starts a code block. |
| 51 | +- Alert descriptions, suggestions and license findings are collapsed onto a |
| 52 | + single line so multi-line API text cannot break the table markup either. |
| 53 | +- When a pull request has no alerts left to report, the security comment is |
| 54 | + replaced with a short confirmation instead of keeping the "Caution" banner |
| 55 | + above a table with no rows. This happens both when a later commit resolves |
| 56 | + every alert and when every alert is ignored by comment. The comment marker is |
| 57 | + preserved, so a commit that reintroduces an alert updates the same comment |
| 58 | + rather than posting a second one. |
| 59 | +- `@SocketSecurity ignore-all` now applies to comments written by CLI versions |
| 60 | + before 2.0.55, which use the older Markdown alerts table. The check was made |
| 61 | + once per ignore command, and an ignore-all comment produces none, so no rows |
| 62 | + were removed. |
| 63 | + |
| 64 | +### Fixed: `--disable-security-issue` and `--disable-overview` now suppress the comment entirely |
| 65 | + |
| 66 | +- Both flags were checked only after testing whether a comment of that type was |
| 67 | + already on the pull request, so they suppressed the first post and then |
| 68 | + updated that comment on every later run. `--disable-security-issue` in |
| 69 | + particular kept refreshing an existing comment with the full alerts table. |
| 70 | +- The flags now mean the CLI does not manage that comment at all. An existing |
| 71 | + comment is left untouched rather than being rewritten, since a body claiming |
| 72 | + no alerts would be inaccurate when reporting is merely switched off. |
| 73 | +- The decision moved into `should_write_comment()` so it is covered directly by |
| 74 | + tests. |
| 75 | + |
17 | 76 | ## 2.6.11 |
18 | 77 |
|
19 | 78 | ### Changed: bump pinned @coana-tech/cli to 15.10.32 |
|
45 | 104 | - Bumped the pinned reachability engine (`@coana-tech/cli`) from `15.10.23` to |
46 | 105 | `15.10.25`. See the [Coana changelogs](https://docs.coana.tech/changelogs) for |
47 | 106 | engine changes. |
48 | | - |
49 | 107 | ## 2.6.7 |
50 | 108 |
|
51 | 109 | ### Changed: bump pinned @coana-tech/cli to 15.10.23 |
|
0 commit comments