Harden .NET supply chain with SBOMs, Trivy scan, provenance, and artifact attestation #54
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This PR introduces a comprehensive supply chain security upgrade for the build and release process of this repository.
The goal: ensure all published packages are verifiably authentic, free of known vulnerabilities, and fully traceable, following industry best practices (SBOM, provenance, and attestation).
Summary of Changes
GitHub Actions pipeline hardening:
contents,packages,id-token,attestations).Nuke build enhancements:
.nupkgand.snupkg), with aggregate SHA256SUMS file for attestation.Best practices documentation:
Why?
How to verify