diff --git a/.gitea/workflows/build.yml b/.gitea/workflows/build.yml
index c707bc8..1936b0d 100644
--- a/.gitea/workflows/build.yml
+++ b/.gitea/workflows/build.yml
@@ -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:
diff --git a/README.md b/README.md
index f144d16..ae2a8d2 100644
--- a/README.md
+++ b/README.md
@@ -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:
 
diff --git a/packaging/alpine/local/greptimedb/README.md b/packaging/alpine/local/greptimedb/README.md
index db6fdb6..3d4ae79 100644
--- a/packaging/alpine/local/greptimedb/README.md
+++ b/packaging/alpine/local/greptimedb/README.md
@@ -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
 ```