Packaging¶
NuGet¶
CryptoService.Sdk is published to nuget.org by
.github/workflows/release.yml on a signed tag, through trusted
publishing (OIDC): the workflow exchanges a short-lived GitHub token for
a NuGet API key in the release environment, with the account name in
the NUGET_USER secret. No long-lived key exists.
Each release ships:
| Asset | What it is |
|---|---|
CryptoService.Sdk.<version>.nupkg |
The library, its XML documentation and the README |
CryptoService.Sdk.<version>.snupkg |
Symbols |
CryptoService.Sdk.<version>.cdx.json |
CycloneDX SBOM |
SHA256SUMS |
SHA-256 of every asset |
and a build provenance attestation for the packages
(gh attestation verify <file> --repo sebastienrousseau/crypto-service-sdk-dotnet).
Package validation¶
Every dotnet pack runs .NET package validation. scripts/api-compat.sh
adds the newest published version older than the one being built (0.0.40
from the 0.0.41 iteration on) as the ApiCompat baseline, so a breaking
change to the public API fails CI.
Reproducing a release¶
REPRODUCING.md rebuilds a released package from its tag and compares it with the GitHub release's assets.
No other distribution¶
No distribution packages (Linux, Homebrew, containers) are claimed: the package is a library, consumed from NuGet.