Pulp Engine Document Rendering
Get started
Release v0.75.5

Release v0.75.5 — ship ci.yml Docker-smoke disk-cleanup

Date: 2026-04-23 Tag: v0.75.5

Summary

One-fix release. Ships the ci.yml docker-build-smoke disk-cleanup fix in a tag commit, which unblocks future tag-push releases from getting stuck on “no space left on device” during Docker image export.

No runtime changes. No API, schema, CLI, or installer changes. This release exists because v0.75.4’s tag commit CI hit the disk-space issue and the fix landed on main post-tag — re-running CI on the v0.75.4 tag commit would still use the pre-fix ci.yml.

This also carries forward all v0.75.4 content (RenderStreamingClient.cs restoration, Go package-name fix) and all prior workflow fixes — anyone who cloned v0.75.4 gets the same shippable surface with a green CI run on the tag commit.

What shipped

ci.yml docker-build-smoke — free disk before image build

ubuntu-latest runners come with ~14 GB free on / after preinstalled toolchains. The Pulp Engine main image bundles Node + Chromium + all workspace packages with their deduplicated dependencies; at export time the full image is materialized to the local daemon (load: true in docker/build-push-action) and the runner runs out of disk.

Added a cleanup step before docker/setup-buildx-action:

- name: Free up disk space for Docker build
  run: |
    sudo rm -rf /usr/share/dotnet /usr/local/lib/android /opt/ghc
    sudo rm -rf /opt/hostedtoolcache/CodeQL
    sudo docker image prune -af
    sudo apt-get clean

Frees ~25-30 GB. Nothing in docker-build-smoke uses dotnet / Android SDK / Haskell / CodeQL.

Only ci.yml needed this fix. release.yml’s docker job uses push: true which streams directly to GHCR without filling local disk (proven by v0.75.3’s successful Release).

Operational status

v0.75.4 deliverables unchanged at v0.75.5 (all carried forward):

  • ✅ TypeScript SDK — same @pulp-engine/sdk + template-model surface
  • ✅ .NET SDK — RenderStreamingClient.cs intact
  • ✅ Go SDK — package pulpengine (valid Go identifier)
  • ❌ PyPI — still blocked on trusted-publisher config

Verification

Local: node scripts/check-version.mjs passes; pnpm lint + pnpm typecheck clean; pnpm sdk:generate regenerates with 0.75.5 correctly.

CI: next tag push should get a green CI on the tag commit AND a green auto-dispatched Release — first fully-automatic tag-push release cycle since the billing-block recovery, blocked at the final hurdle only by this one-line runner-provisioning fix.