Skip to content

fix: build Docker image as part of release workflow - #45

Merged
Taure merged 1 commit into
mainfrom
fix/docker-release-job
Apr 4, 2026
Merged

fix: build Docker image as part of release workflow#45
Taure merged 1 commit into
mainfrom
fix/docker-release-job

Conversation

@Taure

@Taure Taure commented Apr 4, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Move Docker build from standalone docker.yml into release.yml as a needs: release job
  • Remove docker.yml (no longer needed)

GITHUB_TOKEN events (tags, releases) don't trigger other workflows. The only way to chain release → Docker is within the same workflow.

Test plan

  • Merge, verify next release builds and pushes Docker image

GITHUB_TOKEN events don't trigger other workflows, so the separate
docker.yml never fired on release. Move Docker build into release.yml
as a job that runs after the release is created.
@Taure
Taure merged commit 18f7676 into main Apr 4, 2026
15 checks passed
@Taure
Taure deleted the fix/docker-release-job branch April 4, 2026 12:05
Taure added a commit that referenced this pull request Aug 6, 2026
ghcr.io/widgrensit/asobi:0 points at a 2026-04-06 build - pre-Lua-merge,
pre-console - while :latest is current. The tag was published by a
workflow deleted in #45 and nothing has republished it since, so the
floating major, which is what a careful operator pins, silently serves
April code that boots and looks fine.

This workflow emitted {{version}} and {{major}}.{{minor}} but never
{{major}}, so it could never take that tag over. It does now.

A major pin is still weak on a 0.x line where minors are not compatible;
guides/self-hosting.md steers readers to a minor or a digest. This is
about the tag not being actively wrong.
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