Repository navigation
Bump cyclonedx from 6.2.0 to 6.3.1 - #22
dependabot[bot] wants to merge 1 commit into
Conversation
--- updated-dependencies: - dependency-name: cyclonedx dependency-version: 6.3.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
ECC Tools / Security EvidenceCommit: Security evidence gate passed (success) No security-sensitive scanner-evidence gap detected. Mode: enforce Scanned 1 changed file(s). No missing scanner-evidence signal was detected. Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / PR Risk TaxonomyCommit: PR taxonomy clear (success) Scanned 1 changed file(s). No taxonomy bucket signals were detected. Scanned 1 changed file(s). No PR taxonomy bucket signals were detected. Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Reference Set ReadinessCommit: Reference set readiness gaps detected (neutral) Reference evidence present for 0/7 areas (0%) across 1 changed file(s). This check is based on files changed in this PR. Repository-level readiness is still reported by
Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
ECC Tools / Hosted Promotion ReadinessCommit: Hosted promotion readiness passed (success) No hosted promotion evidence gaps detected across 1 changed file(s); 0 corpus scenarios had matching evidence. This check compares PR file changes against the evaluator/RAG promotion corpus in No evaluator corpus scenarios matched this PR. Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission. |
Updated cyclonedx from 6.2.0 to 6.3.1.
Release notes
Sourced from cyclonedx's releases.
6.3.1
Fixed
Fixes a regression in 6.3.0 where
Microsoft.ML.OnnxRuntime.Gpuand its managed/native dependencies were classified as development-only and removed by--exclude-dev(#1139, #1140).Build-only runtime aggregation wrappers are now retained as
Requiredwhen their restored dependency closure provides positive evidence in an allowed runtime-capable category. The refinement is target-local and preserves explicit development-only asset selections, standalone build-only/analyzer/tool filtering, test-only exclusion, and production runtime sharing.Intentional limitation
Restored dependency graphs cannot distinguish every runtime wrapper from a build-tool wrapper with the same observable assets. Conservative retention may therefore also retain ambiguous build-tool closures.
PrivateAssetscontrols propagation, not development intent, and alone does not guarantee exclusion. This is not an exact publish-output scanner.Validation
Cross-platform .NET CI and Docker E2E tests pass. A real consumer referencing only
Microsoft.ML.OnnxRuntime.Gpu1.25.1 was also restored and published forlinux-x64; native runtime loading and XML/JSON SBOM closure retention with--exclude-devwere verified. GPU inference was not tested.Thanks
Thank you @wahyuen (Wah Yuen) for reporting the regression and providing the reproduction details!
Update
Docker image:
cyclonedx/cyclonedx-dotnet:6.3.1(also published aslatest).6.3.0
Added
--set-nuget-purlwith--include-project-referencesgenerates missing project purls. Existing purls and custom BOM references are preserved, and dependency edges use the final references.Changed
scope="excluded". Packages shared with production runtime use remainrequired.--exclude-devis deprecated but continues to filter: it omits development-only and test-project-only packages while retaining packages shared with production runtime use.Fixed
$(RootNamespace)in assembly names, including nested$(MSBuildProjectName)tokens. Missing, empty, or circular$(AssemblyName)-referencing namespaces fall back to the project filename. This is best-effort substitution, not full MSBuild evaluation.--exclude-filterremoves only packages it newly orphans; pre-existing orphans are retained.net48,netstandard2.0,Net8.0, and Windows-qualified TFMs. The underlying NuGet.ProjectModel 7.6.0 fix was already included in 6.2.1.Contributors
Thanks to everyone who contributed code, tests, and issue reports to this release:
🎉 New Contributors
A warm welcome and a big thank you to our first-time contributors:
Full changelog: CycloneDX/cyclonedx-dotnet@v6.2.1...v6.3.0
6.2.1
CycloneDX for .NET 6.2.1
This patch release fixes dependency resolution in multi-project solutions and hash computation for uncached NuGet packages.
Fixed
Sequence contains more than one matching elementwhen multiple merged package versions satisfy an unresolved NuGet dependency range. The BOM now retains a dependency edge to every matching component..nupkg.Changed
Documentation
Contributors
Thanks to everyone who contributed to this release:
Full changelog: CycloneDX/cyclonedx-dotnet@v6.2.0...v6.2.1
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)