fix: add HOST=0.0.0.0 to Dockerfile for probot v14 Docker compatibility

[Copilot]

Summary

Fixes the failing Create pre-release workflow (job 68178180188).

Root Cause

Probot was upgraded from v13 to v14 (a breaking change). One of the breaking changes in probot v14 is:

HTTP Server no longer listens on 0.0.0.0 by default
The built-in HTTP server will now listen on localhost by default, instead of listening on all available interfaces.

When running inside Docker with -p 3000:3000, the app must bind to 0.0.0.0 (all interfaces) for the port mapping to work. With probot v13, the server listened on 0.0.0.0 by default so Docker port mapping worked fine. With probot v14, the server only listens on 127.0.0.1 inside the container — making it unreachable from outside the container — which caused the curl http://localhost:3000 health check to fail with Connection refused.

This is why 2.2.0-rc.2 (using probot v13) worked but the current main-enterprise branch (using probot v14) failed.

Fix

Add ENV HOST=0.0.0.0 to the Dockerfile. This sets the HOST environment variable that probot v14 uses to determine the bind address, restoring the previous Docker-compatible behavior.

ENV NODE_ENV production
ENV HOST=0.0.0.0

[Copilot]

Pull request overview

This PR updates the container runtime configuration to restore Docker port-mapping compatibility after upgrading to Probot v14, which now binds its HTTP server to localhost by default.

Changes:

• Set HOST=0.0.0.0 in the Dockerfile so the Probot server binds to all interfaces inside the container.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.