Watch

windows-msi / full-msi-unsigned (push) Has been cancelled

Details

feat: fill-manifest-sha256.ps1 + CERT local font-face first

Hash helper for DOWNLOADS-MANIFEST; certificate.html prefers fonts/*.woff2 when present.

2026-10-14 00:27:11 -04:00

4.1 KiB

Raw Blame History

Downloads manifest — printit.verae.ai

Human-readable companion to DOWNLOADS-MANIFEST.txt (SHA256SUMS-style lines for live CDN blobs).

HelperVersion (source of truth): internal/job.HelperVersion = 0.3.6
Last-published CDN blobs: mostly 0.3.2 (Windows amd64 NSIS / macOS / Linux) or 0.1.2 (Windows arm64, .deb, bare .zip).
Rule: do not replace a checksum line until the matching artifact is built, signed (when required), uploaded, and the digest verified. TBD is intentional — not a shipping claim.

Related: DUAL-SHIP.md · VM-DUAL-SHIP-CHECKLIST.md · COMMERCIAL-INSTALLER-BACKLOG.md · fill-manifest-sha256.ps1 (local hash → manifest row; does not upload).

0.3.6 — Windows dual-ship (planned; placeholders)

Artifact	Channel	Role	sha256	Status
`VeraePrintStamp-windows-amd64-0.3.6-setup.exe`	NSIS	Primary full-product Windows install (until thin-NSIS exit A–D)	TBD	Not built/uploaded
`VeraePrintStamp-windows-arm64-0.3.6-setup.exe`	NSIS	Full-product arm64 setup	TBD	Not built/uploaded
`VeraePrintStamp-windows-amd64-0.3.6.msi`	Full MSI	Dual-ship / fleet path (`Product-Full` + `build-full-msi.ps1`)	TBD	CI may produce unsigned artifact only
`VeraePrintStamp-windows-arm64-0.3.6.msi`	Full MSI	arm64 elevated MSI (when light path supports arch)	TBD	Not published
`verae-print-windows-amd64-0.3.6.exe`	Bare helper	Optional companion (parity with 0.3.1/0.3.2 EXE rows)	TBD	Not required for dual-ship gate

Do not promote MSI as site primary download until Authenticode + VM C parity + thin-NSIS checklist. Unsigned CI MSI is for clean-VM B smoke only.

Placeholder lines (copy into `.txt` when ready to fill digests)

TBD  VeraePrintStamp-windows-amd64-0.3.6-setup.exe
TBD  VeraePrintStamp-windows-arm64-0.3.6-setup.exe
TBD  VeraePrintStamp-windows-amd64-0.3.6.msi
TBD  VeraePrintStamp-windows-arm64-0.3.6.msi
TBD  verae-print-windows-amd64-0.3.6.exe

After upload (hash only — this helper does not upload):

# Windows (preferred): SHA256SUMS-style rows for DOWNLOADS-MANIFEST.txt
powershell -NoProfile -ExecutionPolicy Bypass -File platform\windows\scripts\fill-manifest-sha256.ps1 `
  -Path .\VeraePrintStamp-windows-amd64-0.3.6-setup.exe,
        .\VeraePrintStamp-windows-amd64-0.3.6.msi
# -Format both  → also print Markdown table rows for this file
# -AsName <cdn-leaf> when local build name ≠ reserved CDN filename

# From the directory that holds the release blobs (POSIX equivalent):
shasum -a 256 VeraePrintStamp-windows-amd64-0.3.6-setup.exe \
  VeraePrintStamp-windows-amd64-0.3.6.msi
# Paste hex digests over TBD in DOWNLOADS-MANIFEST.txt (and this table).

Helper: fill-manifest-sha256.ps1 · dual-ship runbook: DUAL-SHIP.md.

Last-published (live checksums in `.txt`)

Series	Notes
Windows amd64 NSIS `*-0.3.2-setup.exe`	Live primary setup; sha256 in `.txt`
Windows amd64 bare `verae-print-windows-amd64-0.3.2.exe`	Live companion EXE
macOS `VeraePrintStamp-0.3.2.pkg` / `VeraePrintStamp-macos.pkg`	Live
Linux amd64/arm64 `*-0.3.2.tar.gz`	Live
Windows arm64 / `.deb` / `.zip`	Still 0.1.2 on CDN

Exact digests: see DOWNLOADS-MANIFEST.txt.

Operator notes

Site product string may say 0.3.6 while CDN still serves 0.3.2 — that lag is documented on index.html and here.
Filling TBD without uploading the blob breaks mirror checks; always upload first, hash second (fill-manifest-sha256.ps1), rewrite third.
Dual-ship print checklist for clean VMs: VM-DUAL-SHIP-CHECKLIST.md.

4.1 KiB Raw Blame History Unescape Escape