Subject: Production builds stuck in "Blocked/Building" status for 24+ hours

Project: hogganrobbie-1728s-projects / forge-stack (production)
Latest commit on main: a75580d (with new adad002 changes - GUMROAD→LEMONSQUEEZY rename + /api/lemonsqueezy/webhook route)
Multiple production deploys over 24 hours are stuck:

  • dpl_8FbPLv1KzJSA8LfPqDwfg5zWWGoL (Blocked, has new code with HMAC webhook route, returns 302 on GET)
  • dpl_CfKz755g12hQAbCSMBAxydeRPVSR (Blocked)
  • dpl_6NTj74ELPyEXZuyER45qM4FNNC3z (Blocked)
    The only deployment currently marked Current is dpl_4jdXxsqgWv45z3YLdwxJVdvdNB8J which
    was built from old commit fb66c5a (before the Gumroad-to-LemonSqueezy rename).
    Result: pricing page shows “Request X access” mailto fallback instead of “Buy X” buttons.
    Build logs, environmental state, and CLI attempts have all been verified on our end:
  • npm test passes (5/5)
  • Local npm run build clean (17.7s, 13 routes)
  • GitHub HEAD a75580d contains the expected code changes
  • 4 env vars set on the project (NEXT_PUBLIC_LEMONSQUEEZY_*_URL)
    Request: please manually promote dpl_8FbPLv1KzJSA8LfPqDwfg5zWWGoL to production,
    or trigger a fresh build of main (HEAD a75580d). The build workers appear to be
    stuck for this project.
    Thanks.