Skip to content

chore(image): lock the gateway image published for 0.0.3 - #22

Merged
antoinetoussaint-byte merged 1 commit into
mainfrom
chore/lock-gateway-image-0.0.3
Oct 13, 2026
Merged

antoinetoussaint-byte merged 1 commit into
mainfrom
chore/lock-gateway-image-0.0.3

Conversation

@antoinetoussaint-byte

Copy link
Copy Markdown
Contributor

Step 2 of the release order in #21: adopt the gateway image published for 0.0.3 before codefly publish patch tags v0.0.3.

  • Source: publish-gateway-image run 38421130794, dispatched on main c38e940a (build(deps): move to core v0.19.4 #21, core v0.19.4) with version=0.0.3. It succeeded.
  • Change: gateway-image.json is that run's gateway-image.json-0.0.3 artifact, copied unedited: ghcr.io/codefly-dev/service-warehouse@sha256:9f04716e902697027f39b21bdc48b3e867e66447a37bf096ff7c8c146659d7c8.
  • Why it's needed: release.yml's locked-image check refuses a v0.0.3 tag until this lock is on main, and CI inventories both platforms for the locked digest.

This follows the same pattern as #16 for 0.0.2. Classification: fix, the release procedure's own step.

Refs #20

🤖 Generated with Claude Code

publish-gateway-image run 38421130794 on main c38e940 (#21, core v0.19.4)
published ghcr.io/codefly-dev/service-warehouse@sha256:9f04716e902697027f39b21bdc48b3e867e66447a37bf096ff7c8c146659d7c8,
labelled 0.0.3. This is its gateway-image.json artifact, unedited. release.yml
refuses a v0.0.3 tag until this lock is on main.

Refs #20

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@antoinetoussaint-byte
antoinetoussaint-byte merged commit de05f4f into main Oct 13, 2026
4 checks passed
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.

1 participant