Remove `build.binary`. It can be a two liner Dockerfile if absolutely necessary #330

New issue

Closed

opened 2026-06-29 02:11:55 +00:00 by ryansquared · 2 comments

ryansquared commented

2026-06-29 02:11:55 +00:00

(Migrated from codeberg.org)

build {
    binary = "whatever"
}

keeps introducing complexity. It's only useful for statically linked programs, and I doubt enough people are going to want it to require using it. If they really want, they can do the following in a Containerfile:

FROM scratch
COPY ./binary /usr/bin/binary

```hcl build { binary = "whatever" } ``` keeps introducing complexity. It's only useful for statically linked programs, and I doubt enough people are going to want it to require using it. If they really want, they can do the following in a Containerfile: ```dockerfile FROM scratch COPY ./binary /usr/bin/binary ```

caution-bot commented

2026-07-10 01:02:15 +00:00

(Migrated from codeberg.org)

PR #263 made build.binary optional for local app builds, which partially reduced the complexity around this field, but it did not implement the removal requested here. Current main still accepts and documents/tests build.binary/binary in src/caution-config, the Procfile migrator, CLI build paths, and e2e fixtures. Keeping this open until the active config surface is removed (with any compatibility/docs/test updates needed for old configs).

PR #263 made `build.binary` optional for local app builds, which partially reduced the complexity around this field, but it did not implement the removal requested here. Current `main` still accepts and documents/tests `build.binary`/`binary` in `src/caution-config`, the Procfile migrator, CLI build paths, and e2e fixtures. Keeping this open until the active config surface is removed (with any compatibility/docs/test updates needed for old configs).

caution-bot commented

2026-07-13 22:16:21 +00:00

(Migrated from codeberg.org)

Fixed by merged PR #372. Verified on current main that build.binary is rejected in caution.hcl, legacy Procfile binary entries no longer create a build block, and the active API/CLI remote-builder request surface no longer sends binary_path for new deployments. Legacy manifest reader compatibility remains intentionally preserved for already-produced manifests.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

public/platform#330

No description provided.

Rows
Columns

Remove build.binary. It can be a two liner Dockerfile if absolutely necessary #330

Remove `build.binary`. It can be a two liner Dockerfile if absolutely necessary #330