Migrate ARM64 image builds to Forgejo registry #1
Loading…
Reference in a new issue
No description provided.
Delete branch "forgejo-actions"
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?
Move the build workflow and funding configuration from
.githubto.forgejo. Preserve release-tag publishing with full version, eight-character commit, andlatestimage tags atgit.westergaard.cloud/klafbang/nginx-php-fpm.Build only
linux/arm64on the existingk8s-dind-arm-largerunner using Forgejo contexts, output files, and the automatic workflow token. Remove QEMU and Docker Hub credentials. Add manual build validation without publishing images. PHP remains 8.2.7 in this merged change.Validation: YAML parsing, shell image-tag generation, and diff checks passed. The remote validation passed checkout, image tag generation, native ARM64 Docker verification, Buildx setup, and automatic-token registry login. Full image build validation was not completed in this pull request.
Migrate ARM64 image builds to Forgejo registryto Migrate ARM64 builds to Forgejo and update PHP/Alpine baseMigrate ARM64 builds to Forgejo and update PHP/Alpine baseto Migrate ARM64 image builds to Forgejo registry