ci: build an installable Blender zip as a release artifact
"Release" means two different things in this stack and only one of them makes a
file. `pgh publish .` appends metadata (name, version, treeHash, deps) to
pgh-sidecar's ReleaseRegistry so `pgh app install` can content-address the tree
— it never produces a zip, which is why an app with registry releases still
shows an empty repo releases page. The forge's own build-release, driven by
this ci.yaml on push, is what puts a downloadable file there.
So this builds the zip and declares it under `artifacts:`. Layout is a single
top-level hardops/ directory holding blender_manifest.toml — what Blender's
"Install from Disk" expects, matching the vendor zip's own shape.
No `pgh publish` step: publishing propagates fleet-wide on autoupdate and is
permanent, so it stays a deliberate act rather than a consequence of a push.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
6603b0ec9d801290630b2a86300b78d6ec31b355
by plankatron <fleeky@gmail.com> · 2026-08-07T22:06:28.000Z