v0.14.2

Fly.io self-serve runs now produce reports

Two bugs were silently breaking fly machine run against the published ghcr.io/sandgardenhq/find-the-gaps image. With both fixed, the self-serve Fly flow now runs end-to-end and uploads a presigned report URL.

Hugo build was failing inside the container (no error surfaced)

The Dockerfile pinned Hugo 0.140.2, but the bundled Hextra theme declares min_version = 0.146.0. Every Fly run was aborting Hugo with no diagnostic visible to the user because hugo was invoked with --quiet.

• Bump HUGO_VERSION in the Dockerfile to 0.151.0.
• Drop --quiet from the hugo invocation in internal/site/site.go so future build failures surface the actual error instead of a bare exit status 1.
• Update the fly machine run example in the README to pass --vm-cpus 4 --vm-memory 8192. Without them, Fly Machines fall back to shared-cpu-1x:256MB, which OOMs partway through analysis.

Report upload step couldn't find the report

ftg analyze's --cache-dir defaults to the relative path .find-the-gaps, so on Fly it wrote reports to /.find-the-gaps/<repo>/. The run-job.sh upload step looked under $HOME/.find-the-gaps/<repo>/, didn't find site/, and aborted before uploading to Tigris.

• Pass --cache-dir "$HOME/.find-the-gaps" to ftg analyze so both sides agree on the path. The tarball + aws s3 cp + presign steps now run to completion.

Plus the CI fix from v0.14.1

Guard job that prevents publish-image from building the same commit twice on git push --follow-tags.

What's Changed

• ci(image): skip duplicate publish-image run on release-tag pushes by @britt in #97
• fix(fly): bump Hugo to 0.151.0 and surface build errors by @britt in #98
• fix(fly): pin analyze --cache-dir so report upload step finds outputs by @britt in #99

Full Changelog: v0.14.0...v0.14.2