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 dac1832
Browse filesBrowse the repository at this point in the historyBrowse files
fix(manifest): skip .NET where no SDK runs, anchor its exclusions at the scan root
- --auto-manifest, dynamic SBOM inference and the setup wizard skip .NET
builds with one warning where no .NET SDK runs, instead of failing scans
of repositories that only carry a stray project file; an explicit
`socket manifest dotnet` still fails.
- --exclude-paths reaches a solution's projects outside its own directory:
for tools whose builds reach projects anywhere, patterns stay relative to
the scan root, in both generation and the setup wizard.
- An unreadable solution is skipped only when its twin is readable, so two
unreadable twins no longer skip each other silently.
- The setup wizard detects .NET build roots; messages and help name .NET.
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
### Added
10
10
-`socket manifest dotnet`[beta] generates Socket facts files for .NET solutions and projects from your own `dotnet restore`, covering PackageReference (central package management and lock files included) and packages.config projects.
11
-
-`socket manifest auto`, `socket manifest setup` and `--auto-manifest` now detect .NET solutions and projects.
11
+
-`socket manifest auto`, `socket manifest setup` and `--auto-manifest` now detect .NET solutions and projects, and skip them with a warning where no .NET SDK is installed.
12
12
13
13
### Fixed
14
14
-`--exclude-paths` now also excludes modules a build reaches outside its own directory, such as Maven `../` modules and relocated Gradle projects, when Socket facts are generated for each build root.
'Generates dynamic SBOMs via the Gradle/sbt/Maven package manager tools for more accurate results than static resolution. Scans every build root under CWD first, so the configurator only asks about ecosystems actually found; --exclude-paths matches are bulk-disabled, others configured individually.',
39
+
'Generates dynamic SBOMs via the Gradle/sbt/Maven/.NET package manager tools for more accurate results than static resolution. Scans every build root under CWD first, so the configurator only asks about ecosystems actually found; --exclude-paths matches are bulk-disabled, others configured individually.',
--default-on-read-error If reading the socket.json fails, just use a default config? Warning: This might override the existing json file!
27
-
--dynamic-sbom-inference Generates dynamic SBOMs via the Gradle/sbt/Maven package manager tools for more accurate results than static resolution. Scans every build root under CWD first, so the configurator only asks about ecosystems actually found; --exclude-paths matches are bulk-disabled, others configured individually.
27
+
--dynamic-sbom-inference Generates dynamic SBOMs via the Gradle/sbt/Maven/.NET package manager tools for more accurate results than static resolution. Scans every build root under CWD first, so the configurator only asks about ecosystems actually found; --exclude-paths matches are bulk-disabled, others configured individually.
28
28
--exclude-paths Build roots matching these glob patterns (and everything beneath them) are marked disabled. Patterns are anchored micromatch globs matched relative to CWD: \`legacy\` matches only \`<cwd>/legacy\`; use \`**/legacy\` to match at any depth. Negation patterns (\`!path\`) are not supported. Accepts a comma-separated value or multiple flags.
29
29
30
30
This command will try to detect all supported ecosystems in given CWD. Then
0 commit comments