ci: rename build-oci-image.yml to build-windows.yml #29

Merged

David merged 2 commits from chore/rename-build-windows-workflow into main

2026-05-15 03:17:46 +02:00

David commented

2026-05-15 03:16:07 +02:00

Owner

Summary

build-oci-image.yml does not build or push an OCI image. The Dockerfile is a build tool: it cross-compiles a Windows .exe via mingw and the workflow exports the binary via BuildKit's --output type=local, then publishes it to the Forgejo Generic Package registry. Rename the file to build-windows.yml to match the youtrack-cli sibling naming for Windows-only binary publishers (a8n-run/youtrack-cli/.forgejo/workflows/build-windows.yml), and fix the path-self-reference in the trigger filter.

The Dockerfile, oci-build/ directory, and the rest of the workflow body are unchanged. oci-build/ is left as-is because every Rust sibling uses that directory name even when the Dockerfile only exports a binary; renaming would diverge from the cross-repo convention without changing what the directory holds.

Test plan

No other refs to build-oci-image remain (grep -rn build-oci-image clean).
First post-merge push to main runs the renamed Build Windows binary workflow (visible at https://dev.a8n.run/pandoras-box/explorer-bookmarks/actions) and lands the binary at https://dev.a8n.run/api/packages/pandoras-box/generic/explorer-bookmarks/{v0.3.3,latest}/explorer-bookmarks-x86_64.exe.

## Summary `build-oci-image.yml` does not build or push an OCI image. The Dockerfile is a build tool: it cross-compiles a Windows `.exe` via mingw and the workflow exports the binary via BuildKit's `--output type=local`, then publishes it to the Forgejo Generic Package registry. Rename the file to `build-windows.yml` to match the `youtrack-cli` sibling naming for Windows-only binary publishers (a8n-run/youtrack-cli/.forgejo/workflows/build-windows.yml), and fix the path-self-reference in the trigger filter. The Dockerfile, `oci-build/` directory, and the rest of the workflow body are unchanged. `oci-build/` is left as-is because every Rust sibling uses that directory name even when the Dockerfile only exports a binary; renaming would diverge from the cross-repo convention without changing what the directory holds. ## Test plan - [x] No other refs to `build-oci-image` remain (`grep -rn build-oci-image` clean). - [ ] First post-merge push to `main` runs the renamed `Build Windows binary` workflow (visible at `https://dev.a8n.run/pandoras-box/explorer-bookmarks/actions`) and lands the binary at `https://dev.a8n.run/api/packages/pandoras-box/generic/explorer-bookmarks/{v0.3.3,latest}/explorer-bookmarks-x86_64.exe`.

David added 1 commit

2026-05-15 03:16:07 +02:00

ci: rename build-oci-image.yml to build-windows.yml

Check / fmt + clippy + build + tests (pull_request) Failing after 5s

Details

7ad0fa2d6e

The workflow does not build or push an OCI image; it cross-compiles a Windows .exe via mingw and publishes it to the Forgejo Generic Package registry. Match the youtrack-cli sibling naming for Windows-only binary publishers, and fix the path-self-reference in the trigger filter.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

David added 1 commit

2026-05-15 03:16:24 +02:00

ci: update path-self-reference in build-windows.yml

Check / fmt + clippy + build + tests (pull_request) Successful in 5s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

3c8089854c

Missed in the rename commit: the workflow's own paths filter still pointed at the old build-oci-image.yml filename, which would have prevented edits to this workflow file from triggering itself.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>