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 d283907
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(scan): fail closed without a .NET SDK, simplify facts-only wiring
- --dynamic-sbom-inference and its setup wizard fail closed when no .NET
SDK runs for a .NET build root, for every consumer, since no facts can
be generated without it. --auto-manifest still warns and skips.
- Name socket.json's path and the setup command in the next steps.
- Write the reachability sidecar whenever facts-only types are set, so
the flag and the sidecar `coana run` needs come from the same input.
- Name the upload-only inference mode instead of an undefined consumer.
- Move useOnlySocketFactsArtifactsFlags next to the other Coana helpers.
- Table-driven tests with shared helpers.
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
@@ -8,7 +8,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
8
8
9
9
### Changed
10
10
- 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.
11
-
-With `--dynamic-sbom-inference`, reachability analysis and `socket fix` now stop with clear next steps when a .NET build cannot be read because no .NET SDK is installed, and warn that builds skipped in `socket.json` are left out. Reachability analysis also stops with next steps when no build produced Socket facts.
11
+
-`--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.
`No .NET SDK runs for ${displayPath(buildRootPath(root))} (${reason}), so it has no Socket facts, and the analysis takes .NET dependencies only from them.`,
222
+
`No .NET SDK runs for ${displayPath(buildRootPath(root))} (${reason}), so its Socket facts cannot be generated.`,
225
223
'',
226
-
'- Install the .NET SDK, or point defaults.manifest.dotnet.bin in socket.json at one.',
227
-
'- Or leave it out with --exclude-paths, or with defaults.manifest.dotnet.disabled in socket.json.',
224
+
`- Install the .NET SDK, or point defaults.manifest.dotnet.bin in ${socketJson} at one (\`${DSI_SETUP_COMMAND}\` walks you through it).`,
225
+
`- Or leave it out with --exclude-paths, or with defaults.manifest.dotnet.disabled in ${socketJson}.`,
0 commit comments