chore(deps): update weight-custody-manifest requirement from >=0.28.0 to >=0.28.1

[dependabot]

Updates the requirements on weight-custody-manifest to permit the latest version.

Release notes

Sourced from weight-custody-manifest's releases.

WCM 0.28.1 fixes SEV-SNP report verification when the VCEK certificate is signed by an RSA-PSS issuer. Report verification now uses ECDSA P-384/SHA-384 independently of the certificate issuer's signature parameters. Unsupported combinations return a failed verification result.

Thanks to Zoheb Shaik for reporting the defect and supplying the SEV-SNP hardware reproduction used to confirm it.

The reference JSON parser defaults to ECDSA/SHA-256. Configure another supported report profile explicitly; issuer metadata no longer selects the report algorithm.

This release also restores public Source, Issues and Changelog package links, fixes documentation publishing, and removes a device-identifying receipt from the current repository tree. Earlier Git history is unchanged. The original receipt is retained outside the public distribution, and its pinned test skips when unavailable.

Validation on the release PR: 643 tests passed, four skipped, 92.77% coverage; all ten CI checks passed. The built wheel and source archive passed metadata checks. A fresh wheel installation passed all 91 reference conformance vectors. These checks do not establish production readiness or additional hardware assurance.

Install after publication:

python -m pip install weight-custody-manifest==0.28.1

Changelog

Sourced from weight-custody-manifest's changelog.

0.28.1 - 2026-09-08

[fix] SNP report verification now uses the report format's ECDSA P-384 / SHA-384 parameters independently of the VCEK certificate's issuer signature. RSA-PSS-signed VCEKs no longer pass RSA parameters to an elliptic-curve report key. Unsupported signature combinations return a failed verification result. Certificate-chain checks remain separate, including RSA-PSS support.

The reference JSON parser defaults to ECDSA/SHA-256; other report profiles must be selected in parser configuration rather than inferred from certificate issuer metadata. Synthetic regressions cover mixed issuer/report algorithms, altered reports and signatures, untrusted roots, nonce and transport-key mismatches.

Thanks to Zoheb Shaik for reporting the defect and supplying the SEV-SNP hardware reproduction used to confirm it.

[docs/packaging] Restore public source, issues and changelog links in package metadata. Documentation publishing uses the gh-pages branch and preserves the custom domain on each build. Release verification and hardware validation guides now describe reproducible checks without internal coordination details.

[privacy] Remove the device-identifying paired hardware receipt from the current repository tree and remove its scanner exception. The original remains outside the public distribution; its pinned test skips when it is unavailable. The fixture is also excluded if restored locally before a package build. Earlier Git history is unchanged.

0.28.0 - 2026-09-01

[security/packaging] Removed internal infrastructure identifiers from two test-fixture documents under python/tests/fixtures/live-validation/, and added tools/leak_scan.py plus a leak-scan workflow that runs on every push, pull request and published release.

The scan matches identifier shapes rather than a list of known-bad strings: bare GUIDs, cloud resource names, X.509 serialNumber attributes, private-key blocks and cloud access-key IDs. The control it replaces was a manual denylist of named entities, which by construction could not match an identifier it had never been told about, and which only ran when someone remembered to run it. Running in CI also closes the gap that every previous control guarded the repository's visibility, while a package index is reached by twine upload regardless of what that visibility says.

paired-2026-08-20/paired-release.json is the one fixture still carrying a hardware identifier, an Azure SNP/vTPM device serial alongside the H100 model, driver, VBIOS and PCI address. It is SHA-256 pinned by tests/test_paired_hardware_receipt.py, so editing it would break the integrity pin that shows the receipt is the one the hardware produced. Rather than trade the pin against publishability, it is now excluded from the sdist: the pin keeps working in this repository, where the test runs, and the identifier is not

... (truncated)

Commits

• 232834e Prepare 0.28.1 and complete public package metadata (#113)
• 5595486 Fix SNP report signature profile independently of certificate issuer (#112)
• 66e433b Fix documentation publishing and public release guidance (#111)
• See full diff 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)