2 posts tagged with "content-packs"

The friction​

Through v0.11.0, the canonical recipe for a podcast cover was:

agent → podcast.generate (with generate_cover_prompt:true)
     → reads cover_image_prompt out of the response
     → image.generate(prompt: that-string)
     → reads image_artifact_key
     → pastes URL into the publish step

Four pack calls, two registry round-trips, two audit-log entries, two LLM cost-per-tool-call decisions on the agent's side. And the agent has to remember which model to use for the cover — fal.ai has a dozen, all with different cost/quality trade-offs.

Tag: v0.10.0. Upgrade in 5 min: git checkout v0.10.0 && make install.

v0.10.0 is a content-packs release. The two new packs let an agent generate something it can publish — a blog post via Ghost, a multi-speaker podcast MP3 via ElevenLabs — in one tool call, instead of needing to chain http.fetch + custom JWT logic + ffmpeg shellouts. Pack count climbs from 36 to 38.

It also closes a gap on the operator side: until this release helmdeck had zero documentation on how to upgrade a running install. New docs/howto/upgrade-helmdeck.md covers the in-place Compose upgrade, schema migrations, post-upgrade validation, and rollback. With Kubernetes coming in v1.0, the absence of this guide had become a real risk.