ci: forgejo workflows for next-image builds and tagged releases #5
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/forgejo-workflows"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds Forgejo Actions CI:
.forgejo/workflows/build-next.yaml— push tomain→ multi-arch (amd64/arm64) image pushed asgit.w33ble.com/w33ble/lagom:next.forgejo/workflows/release.yaml— tagv*→ cross-compiled binaries, multi-arch image as:vX.Y.Z+:vX+:latest(rolling tags skipped for prereleases), Forgejo release with binaries attachedCross-compilation uses
actions/setup-go@v7+ nativeGOOS/GOARCHbuilds; images are assembled byDockerfile.ci, which consumes prebuilt binaries (no QEMU/emulation needed).Required secrets before merge (Settings → Actions → Secrets):
REGISTRY_USER— Forgejo usernameREGISTRY_TOKEN— PAT withwrite:package+read:packageRELEASE_TOKEN— PAT withwrite:repositoryREADME updated with a CI/CD section.
876fbe2040cf1bbf3bf0cf1bbf3bf08c4d65cc348c4d65cc34bd2a19405bbd2a19405bddf548c3bdddf548c3bda0720c3c20a0720c3c20bcf6416ea7