Skip to content

CI never builds the container image #56

Description

@SirLouen

Nothing builds the container image until a tag exists, so a broken Dockerfile is invisible until the moment it matters most.

Current state: ci.yml runs test, frontend, lint, vuln and sdk-compat. None of them touches the Dockerfile. Only release.yml builds an image, and it runs on a pushed tag. Dropping the patches directory in #53 left COPY patches ./patches behind, every gate stayed green, the pull request merged, and 0.11.0 failed at the release build with the tag already pushed.

Proposal: add a build only job to ci.yml that builds the image and pushes nothing. The failure above takes seconds to catch and needs no registry credentials.

Trigger: already fired, it broke the 0.11.0 release.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions