Build Alpine packages for stable and edge

README.md

@@ -1,12 +1,13 @@
 # Alpine Packages
 
-Alpine 3.23 packaging for internal packages.
+Alpine stable and edge packaging for internal packages.
 
 This repository builds signed `x86_64` and `aarch64` APKs and publishes them to
-the Gitea Alpine package registry under:
+the Gitea Alpine package registry under stable and edge branches:
 
 ```text
 https://code.factoring.digital/api/packages/public/alpine/v3.23/alpine-packages
+https://code.factoring.digital/api/packages/public/alpine/edge/alpine-packages
 ```
 
 ## Use In Production
@@ -20,7 +21,7 @@ curl -fsSLo /etc/apk/keys/public-alpine.rsa.pub \
   https://code.factoring.digital/api/packages/public/alpine/key
 ```
 
-Add the package repository:
+Add the stable package repository:
 
 ```sh
 printf '%s\n' \
@@ -30,6 +31,16 @@ printf '%s\n' \
 apk update
 ```
 
+Use the edge branch on Alpine edge nodes:
+
+```sh
+printf '%s\n' \
+  'https://code.factoring.digital/api/packages/public/alpine/edge/alpine-packages' \
+  >> /etc/apk/repositories
+
+apk update
+```
+
 If a forked or future registry is private, include a Gitea user and package token in the
 repository URL:
 
@@ -322,9 +333,9 @@ Run `apk:checksum` after changing any file listed in `source=`.
 
 ### Gitea Workflow
 
-The workflow at `.gitea/workflows/build.yml` builds in an `alpine:3.23`
-container and publishes on push or tag. It skips publishing for pull request
-events.
+The workflow at `.gitea/workflows/build.yml` builds a matrix for `alpine:3.23`
+and `alpine:edge`, publishing to registry branches `v3.23` and `edge` on push
+or tag. It skips publishing for pull request events.
 
 Repository variables: