ci: bump agent-manifest from 0.14.0 to 0.15.0

[dependabot]

Bumps agent-manifest from 0.14.0 to 0.15.0.

Release notes

Sourced from agent-manifest's releases.

python-v0.15.0

What's Changed

• fix(sdk): attach_receipt refuses a non-array receipts value instead of corrupting it by @​rajnisht7 in agentrust-io/agent-manifest#469
• docs(changelog): file the attach_receipt fix under Unreleased by @​imran-siddique in agentrust-io/agent-manifest#478
• feat(sdk): add opt-in experimental evidence-requirements profile by @​imran-siddique in agentrust-io/agent-manifest#479
• fix(attestation): refuse debug guests and non-VMPL0 SNP reports, release 0.15.0 by @​imran-siddique in agentrust-io/agent-manifest#480

Full Changelog: agentrust-io/agent-manifest@python-v0.14.0...python-v0.15.0

Changelog

Sourced from agent-manifest's changelog.

[0.15.0] - 2026-09-30

Security

• [SDK] verify_attestation_chain() refuses debug guests. The SEV-SNP path never read the signed guest policy and the TDX path never parsed TDATTRIBUTES, so a debug-enabled guest with an allow-listed measurement returned passed=True. A debug guest's memory is readable and writable by the host, so its REPORT_DATA and the code that chose it are the host's to set. The verdict now fails when SNP guest policy DEBUG (bit 19, AMD 56860) or TDX TDATTRIBUTES.DEBUG (bit 0, TD report body offset 120) is set, read from the signed bytes after the signature verifies. SNP reports must also carry VMPL 0, the level both of this package's SNP producers request at (SEVSNPProvider through configfs-TSM, and the Azure paravisor). verify_runtime_report() and verify_runtime_freshness() apply the same checks with no opt-in. ChainVerificationResult gains debug and vmpl, read from the signed report (None without a verified signature, and for platforms with no such field). verify_attestation_chain(allow_debug=True) accepts a debug guest for development and records it in reasons; it does not relax VMPL. SnpReport.debug, TdxQuote.td_attributes and TdxQuote.debug expose the parsed state. Behaviour change: a debug guest, or an SNP report at VMPL 1 to 3, that previously verified now fails.

Added

• [SDK] Experimental, opt-in evidence-requirements-experimental-v1 profile. A v0.2 manifest that declares it may carry a signed evidence_requirements block (components, required relationships, combination policy reference), and agent_manifest.evidence_requirements.verify_evidence_manifest() returns it only after verify_manifest() is VALID. Without the profile the block is still rejected as an unknown field, so existing manifests verify as before. Under the profile every 0.14.0 check still applies, including the signed audit_key_sealed rule under enforce_attestation. Not part of the specification; see docs/evidence-requirements-experimental.md. Consumer: agentrust-io/trace-spec#439.

Fixed

• [SDK] attach_receipt() corrupted or crashed when the envelope's receipts header (label 394) wasn't already an array - a map became its keys, a string its characters, and null/0/false/"" were silently replaced with []. attach_approvals() was already fixed for the same issue in 0.13.0; attach_receipt() now works the same way: a non-array existing value raises CoseStructureError instead of being coerced or overwritten, and receipt itself must be bytes or bytearray. To replace the array, use attach_unprotected(envelope, HDR_RECEIPTS, receipts). Behaviour change: a bad receipt, or a non-array receipts value, now raises instead of being silently coerced.

Commits

• 2f1b9f5 fix(attestation): refuse debug guests and non-VMPL0 SNP reports, release 0.15...
• 7466b3d feat(sdk): add opt-in experimental evidence-requirements profile (#479)
• 7a28a4b docs(changelog): file the attach_receipt fix under Unreleased (#478)
• d3ed22e fix attach receipt (#469)
• See full diff in compare view

[imran-siddique]

@dependabot rebase

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[imran-siddique]

Dependabot bump. Every check is green apart from the maintainer hold.

[imran-siddique]

@rajnisht7 nine dependabot PRs need a second approval because I pushed fixes to them, which voids mine under the last-push rule. All are green: cmcp#725, #726, #729, #730, agentrust-io/ca2a#226, agentrust-io/ca2a#227, agentrust-io/ca2a#229, agentrust-io/integrations#256, agentrust-io/integrations#267. Each fix is one commit on top of dependabot's (lock regeneration, a test pin, or test expectations). Could you approve them by October 7?