Skip to content

chore: re-pin core to v0.3.6 for CLI-owned build (#20) - #21

Open
antoinetoussaint-byte wants to merge 1 commit into
mainfrom
issue-20-adopt-cli-owned-build-migrate-build-rpc-to
Open

antoinetoussaint-byte wants to merge 1 commit into
mainfrom
issue-20-adopt-cli-owned-build-migrate-build-rpc-to

Conversation

@antoinetoussaint-byte

Copy link
Copy Markdown
Contributor

Closes #20.

Summary

  • S3 is a managed / off-the-shelf image agent: it runs the upstream digest-pinned cgr.dev/chainguard/minio image and has no builder/Dockerfile. Its Build RPC already returns an empty BuildResponse() and never runs docker build, so there is nothing to render into output_directory and no DockerBuildPlan to emit — this is the triage's verify-and-close-as-no-op case.
  • Re-pinned github.com/codefly-dev/core v0.3.4 → v0.3.6 (the release carrying the build-recipe contract and shared runners) to keep this agent on the fleet baseline. No behavior change, so no test change.

Test plan

  • go build ./...
  • go vet ./...
  • go test ./... — pass
  • Confirmed no-op: Build uses an upstream image, no builder/Dockerfile exists, and the RPC performs no in-process docker build.

S3 is a managed off-the-shelf image agent (upstream chainguard/minio,
no builder/Dockerfile), so the Build RPC stays a no-op. Re-pin core to
the release carrying the build-recipe contract to stay aligned with the
fleet.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Adopt CLI-owned build: migrate Build RPC to the build-recipe contract (cli#443)

1 participant