Optimize APK update checks and CI builds
Build Alpine Packages / build-and-publish (v3.24, 3.24) (push) Failing after 2h20m30s

This commit is contained in:
Joachim Schlöffel
2026-08-24 08:51:30 +02:00
parent 9b9473f497
commit 479886d37d
10 changed files with 269 additions and 172 deletions
+7 -2
View File
@@ -92,7 +92,7 @@ apk:lint-shell Run ShellCheck for packaging automation
apk:packages List built Alpine packages and dependencies
apk:publish-check Run lint, multi-arch build, package listing, and smoke test
apk:publish-gitea Publish built packages to the Gitea Alpine package registry
apk:outdated Check packaged upstream versions against latest GitHub releases
apk:outdated Check packaged upstream versions and release summaries
apk:shell Open an Alpine package build shell in Docker
apk:smoke Install-test built packages from the local repository in Docker
apk:test-install Test README installation instructions in a fresh Alpine container
@@ -231,10 +231,15 @@ versions fail the command:
APK_UPDATE_CHECK_MODE=fail mise run apk:outdated
```
When an update is available, the command also lists compact release-note
summaries for every release between the packaged and latest versions.
### Gitea Workflow
`.gitea/workflows/build.yml` builds and publishes `v3.24`. Pull requests
build only.
build only. CI compares source package versions with the published registry,
then rebuilds only changed or unpublished packages; local build commands keep
using their local caches.
Repository variables: