[PR #141] [MERGED] ci(docker): publish each image flavor on its own #132

New issue

Closed

opened 2026-10-18 21:14:37 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-18 21:14:37 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/oikb/pull/141
Author: @walkerobrien-cw
Created: 10/10/2026
Status: ✅ Merged
Merged: 10/10/2026
Merged by: @tjbck

Base: main ← Head: fix/publish-each-flavor

📝 Commits (1)

45e7997 ci(docker): publish each image flavor on its own

📊 Changes

1 file changed (+12 additions, -4 deletions)

View changed files

📝 .github/workflows/docker.yml (+12 -4)

📄 Description

Refs #126.

merge-release and merge-release-alpine both need the whole build-release matrix. So the alpine/arm64 build failing on pymupdf==1.28.2 (it has no musl/arm64 wheel, and building from source fails) also skipped the default-image merge. That merge's digests had built fine, but no 0.5.0, 0.5 or latest tag was published. The dev merges have the same coupling.

This PR changes two things:

Each merge job runs unless the workflow was cancelled (!cancelled()). The release merges also still require read-version to have succeeded.
A merge publishes only when both of its flavor's arches built. It checks for exactly two digests, so a single failed arch can't produce a one-arch manifest.

This doesn't fix the alpine/arm64 pymupdf build itself. That flavor will keep failing, visibly, until it's addressed, but it no longer blocks the default image. Re-running the release workflow afterwards should publish 0.5.0.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/oikb/pull/141 **Author:** [@walkerobrien-cw](https://github.com/walkerobrien-cw) **Created:** 10/10/2026 **Status:** ✅ Merged **Merged:** 10/10/2026 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `main` ← **Head:** `fix/publish-each-flavor` --- ### 📝 Commits (1) - [`45e7997`](https://github.com/open-webui/oikb/commit/45e79971dfab3da3d93903002cf65802380368ee) ci(docker): publish each image flavor on its own ### 📊 Changes **1 file changed** (+12 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/docker.yml` (+12 -4) </details> ### 📄 Description Refs #126. `merge-release` and `merge-release-alpine` both `need` the whole `build-release` matrix. So the alpine/arm64 build failing on `pymupdf==1.28.2` (it has no musl/arm64 wheel, and building from source fails) also skipped the default-image merge. That merge's digests had built fine, but no `0.5.0`, `0.5` or `latest` tag was published. The dev merges have the same coupling. This PR changes two things: - **Each merge job runs unless the workflow was cancelled** (`!cancelled()`). The release merges also still require `read-version` to have succeeded. - **A merge publishes only when both of its flavor's arches built.** It checks for exactly two digests, so a single failed arch can't produce a one-arch manifest. This doesn't fix the alpine/arm64 pymupdf build itself. That flavor will keep failing, visibly, until it's addressed, but it no longer blocks the default image. Re-running the release workflow afterwards should publish `0.5.0`. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-18 21:14:37 +00:00

closed this issue
added the
pull-request
label

No labels

pull-request

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

open-webui/oikb#132

No description provided.

Rows
Columns