Releases: WHY-Daydream/dsh-pack
Release list
v0.6.1 — Latest DSH compatibility fix
v0.6.1 — Latest DSH compatibility fix
Patch release improving compatibility with current DSH 0.1.x prerelease lines.
Fixed
- Fixed npm semver prerelease matching for
@deepseek-ai/dsh-app-boot - Added explicit support for current prerelease tuples:
0.1.0-rc.x0.1.1-rc.x0.1.2-alpha/rc.x0.1.3-alpha.x
0.2.xremains intentionally unsupported pending a separate compatibility review
Compatibility Acceptance
CA-01 ~ CA-08: ALL PASS
- strict npm peer resolution
- current DSH source API compatibility
- real
dsh plugin addpath /packregistration- pack → verify → install golden path
- typecheck
- 434/434 tests
- registry clean-room verification
Artifact
Published npm artifact is byte-for-byte identical to the audited tgz.
dist.shasum:
ee6834201f230219daf2b620fc12b3ec92291335
v0.6.0 — Distributed Verifiable Evidence
OCI Referrers Evidence 分发 + 远程信任(D149–D199 冻结): alpha.1 discovery / alpha.2 publication / alpha.3 cache / beta.1 trust / beta.2 registry interop / rc.1 adversarial matrix / RI-17–RI-28 invariant review。真实 GHCR gate(I8/I9/I10 + R8a/R8b/R8c)与 ORAS 双向 smoke (RG6-09,ORAS-01/ORAS-02)全绿。420/420 tests ALL PASS。 见 CHANGELOG.md [0.6.0]。 Co-Authored-By: AtomCode (deepseek-v4-flash) <noreply@atomgit.com>
v0.5.0 — Verifiable Agent Artifact
Verifiable Agent Artifact
Every critical security assertion is actively attack-tested. The chain:
- Artifact Identity — immutable
contentHash+ Artifact Signature (VALID ≠ TRUSTED) - Build Evidence — Build Provenance (build-time capture) + CycloneDX SBOM (document digest-bound)
- Runtime Evidence — Declared Capability + Runtime Attestation (must exact-match the current execution target)
- Policy — trust.yaml v2: consumes only verified + trusted evidence; conflicting trusted evidence fails closed (
AMBIGUOUS → DENY)
RC Hardening
7 adversarial attack surfaces (N3/N7/N4/N5/N1/N2/N6) · 324 regression tests · 16 frozen release invariants (RI-01–RI-16)
Five real implementation flaws discovered and fixed during rc.1:
- blocked lifecycle execution before trust decisions
- closed an SBOM document-substitution verification gap
- corrected runtime-attestation semantic equivalence (non-deterministic run metadata no longer causes false ambiguity)
- prevented stale local mirrors from hijacking mutable registry tags
- preserved UNKNOWN native metadata instead of fabricating native=false
No new Evidence types · no new trust.yaml features · no encryption · no compatibility engine.
Release gates RG-01–RG-08: all PASS (identity domains kept distinct, npm package boundary audited, clean-room consumer install verified, secrets/credentials scan clean).
dsh-pack v0.4.2 — Distribution Governance
Highlights
- Real GHCR OCI distribution verified 8/8(run 33292227705,2026-08-30)
- image lock: mutable remote tag → immutable OCI manifest digest(D46–D49)
- trust.yaml: repository-scoped execution policy(D50–D56)
- local image prune: mark-and-sweep reachability CAS GC(D57–D63)
Release invariants
- Lock ≠ Trust
- Cache ≠ Trust
- Registry ≠ Trust Authority
- OCI digest ≠ DSH contentHash
- CLI may tighten policy, never weaken it
Pipeline
Snapshot → Portable → Trusted → Runnable → Distributed → Governed