You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6748a9d
Browse filesBrowse the repository at this point in the historyBrowse files
fix(scan): fail a .NET build without an SDK like any other build
Drop the dedicated .NET SDK probe from --dynamic-sbom-inference and its
setup wizard: a missing SDK now fails the build root the way a missing
Maven does, so the run aborts through the usual failed-root path and
--json lists the root. --auto-manifest keeps warning and skipping.
Also write the sidecar whenever the facts-only flag is sent, for fix as
for reach, type the facts-only types as non-empty, and order the result
fields.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
11
11
12
12
### Changed
13
13
- With `--dynamic-sbom-inference`, reachability analysis and `socket fix` now take the dependencies of every Gradle, sbt, Maven and .NET build they find from Socket facts only, so results no longer depend on which other builds produced facts.
14
-
-`--dynamic-sbom-inference` and its setup now stop with clear next steps when a .NET build cannot be read because no .NET SDK is installed, instead of skipping it. With it, reachability analysis and `socket fix` warn that builds skipped in `socket.json` are left out, and reachability analysis stops with next steps when no build produced Socket facts.
14
+
-`--dynamic-sbom-inference` and its setup now fail a .NET build that has no usable .NET SDK, as they do a Maven build without Maven, instead of skipping it. With it, reachability analysis and `socket fix` warn that builds skipped in `socket.json` are left out, and reachability analysis stops with next steps when no build produced Socket facts.
0 commit comments