AsiBackbone 7.1.1 Consumer Verification Guide
This guide records the consumer checks for the 7.1.1 package family. Perform
the artifact-verification steps against the published v7.1.1 GitHub Release
and NuGet packages after publication.
Confirm the compatibility boundary
- Package IDs remain
AsiBackbone.*. - All packages continue to target
net10.0. - Managed assemblies retain
AssemblyVersion7.0.0.0. - Package and file versions are
7.1.1and7.1.1.0. - Package dependencies are the same as in
7.1.0. - No public API, persisted schema, canonical wire value, namespace, or runtime default is changed.
Confirm the patch carries no behavior change
- Replace
7.1.0with7.1.1in a consumer that already builds against7.1.0, restore, and build with warnings enabled. Expect the same diagnostics, including anyASIB004,ASIB902, orASIB903warnings the project already reported. - Run the consumer's own tests. Expect the same results as on
7.1.0. - Open a package README on NuGet.org and confirm it shows that package's version and download badges.
Verify the published packages
Download a package and its release evidence from the v7.1.1 GitHub Release,
then verify its provenance:
gh release download v7.1.1 --repo AsiBackbone/AsiBackbone --pattern 'AsiBackbone.Core.7.1.1.nupkg'
gh attestation verify ./AsiBackbone.Core.7.1.1.nupkg --repo AsiBackbone/AsiBackbone
Inspect the package metadata and Source Link repository commit, and compare the package SHA-256 value with the release evidence manifest. Repeat for each package adopted by the application.
Build a clean consumer
Create a clean net10.0 project, add only the required AsiBackbone.* packages
at 7.1.1, restore, build with warnings enabled, and exercise the integration
boundary used by the application. Consumers upgrading from 6.x must first
complete the 6.x to 7.0 upgrade guide; the analyzer and
deprecation checks for the 7.1 line are in the
7.1.0 Consumer Verification Guide.
See also: