v1.2.0 — Pull Request Previews

Release date: July 18, 2026

PocketStack v1.2.0 centers the product on one workflow: add one GitHub Action and receive a static, shareable preview for every browser-compatible Docker Compose pull request.

One self-contained Action

ramazankara/pocketstack@v1 now checks out the pull request, builds the trusted PocketStack CLI from the selected Action revision, analyzes the Compose project, generates static output, deploys a stable Cloudflare Pages branch alias, and updates one sticky PR comment.

The job summary and outputs expose readiness status, score, stable preview URL, and immutable deployment URL. Closing the pull request replaces the stable alias with a static tombstone.

Compatibility remains non-negotiable

Only ready stacks receive application previews. partial and blocked stacks fail the check and receive a static compatibility report listing each service’s mapping, unsupported reasons, and conversion suggestions. There is no hidden Docker runner or remote-container fallback.

Action inputs and generated reports are hardened for untrusted PR content: project paths and symlinks cannot escape the checkout, rendered strings are capped and escaped, and forks and Dependabot never receive deployment secrets or writable comments.

Three recognizable proof applications

• Pocket Supply storefront — a searchable catalog, fixture API, cart, quantities, and checkout using frontend plus mock-http.
• Northstar sprint board — issue creation, filters, drag-and-drop, keyboard moves, and seeded browser Postgres using frontend plus postgres-pglite.
• Clearview analytics — responsive metrics, SVG charts, date ranges, tooltips, and a sortable table using static-web.

The showcase workflow generates all three with PocketStack and deploys stable Cloudflare Pages branches.

Website and docs

The public site, README, getting-started guide, and compatibility docs now tell the same pull-request story. Ready and blocked report examples are presented side-by-side so the browser-only boundary is visible before installation.

Start with pull request previews or inspect the compatibility matrix.