Add Alpine v3.24 package target
Build Alpine Packages / build-and-publish (v3.23, 3.23) (push) Successful in 26m38s
Build Alpine Packages / build-and-publish (v3.24, 3.24) (push) Successful in 38m1s

This commit is contained in:
Joachim Schlöffel
2026-07-05 23:18:35 +02:00
parent 4efe12f250
commit 1c4b598b5c
3 changed files with 11 additions and 7 deletions
+2
View File
@@ -18,6 +18,8 @@ jobs:
include:
- alpine_version: "3.23"
alpine_registry_branch: "v3.23"
- alpine_version: "3.24"
alpine_registry_branch: "v3.24"
container:
image: "alpine:${{ matrix.alpine_version }}"
env:
+8 -6
View File
@@ -4,6 +4,7 @@ Alpine stable packaging for internal packages.
```text
https://code.factoring.digital/api/packages/public/alpine/v3.23/alpine-packages
https://code.factoring.digital/api/packages/public/alpine/v3.24/alpine-packages
```
## Available Packages
@@ -24,11 +25,11 @@ curl -fsSLOJ https://code.factoring.digital/api/packages/public/alpine/key
Keep the filename returned by Gitea. Alpine matches repository signatures by key filename, otherwise `apk update` reports `UNTRUSTED signature`.
Add the stable package repository:
Add the stable package repository matching the Alpine branch on the node:
```sh
printf '%s\n' \
'https://code.factoring.digital/api/packages/public/alpine/v3.23/alpine-packages' \
'https://code.factoring.digital/api/packages/public/alpine/v3.24/alpine-packages' \
>> /etc/apk/repositories
apk update
@@ -38,7 +39,7 @@ If a forked or future registry is private, include a Gitea user and package toke
repository URL:
```text
https://<user>:<token>@code.factoring.digital/api/packages/public/alpine/v3.23/alpine-packages
https://<user>:<token>@code.factoring.digital/api/packages/public/alpine/v3.24/alpine-packages
```
## Contribution
@@ -201,9 +202,10 @@ Run `apk:checksum` after changing any file listed in `source=`.
### Gitea Workflow
The workflow at `.gitea/workflows/build.yml` builds against `alpine:3.23` and
publishes to registry branch `v3.23` on push or tag. It skips publishing for
pull request events.
The workflow at `.gitea/workflows/build.yml` builds against each stable Alpine
target in its matrix and publishes to the matching registry branch, currently
`v3.23` and `v3.24`, on push or tag. It skips publishing for pull request
events.
Repository variables:
+1 -1
View File
@@ -101,7 +101,7 @@ Install-test from a published Gitea Alpine repository:
```sh
ALPINE_PACKAGE=greptimedb \
SKIP_BUILD=1 \
ALPINE_REPOSITORY_URL=https://code.factoring.digital/api/packages/public/alpine/v3.23/alpine-packages \
ALPINE_REPOSITORY_URL=https://code.factoring.digital/api/packages/public/alpine/v3.24/alpine-packages \
ALPINE_REPOSITORY_KEY_URL=https://code.factoring.digital/api/packages/public/alpine/key \
mise run apk:test-install
```