Port CI to Forgejo Actions
Some checks failed
ci / publish-amweb-version (push) Has been skipped
ci / build-image (push) Has been cancelled

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
Jonas Leder 2026-11-18 10:46:43 +01:00
commit b99f608b69
4 changed files with 129 additions and 311 deletions

119
.forgejo/workflows/ci.yml Normal file
View file

@ -0,0 +1,119 @@
# Builds the diskless Alpine kiosk image. No QEMU / virtualization is needed: build-image.sh only
# runs `apk --root`, mksquashfs and cpio/gzip on a native x86_64 target.
#
# Two update trains, published side by side in the same bucket: stable at the bucket root
# (kiosks in the field point their UPDATE_URL here, see config/kiosk.conf.example) and beta under
# "beta/" (develop branch). Each is baked into its latest.json "url" (ARTIFACT_BASE_URL), so it
# MUST match the prefix the deploy steps publish dist/ to.
#
# RAUC_SIGN_CERT / RAUC_SIGN_KEY: repo secrets with the PEM contents of a persistent cert/key pair.
# Without them build-image.sh falls back to a throwaway dev cert.
#
# MINIO_ENDPOINT / MINIO_ACCESS_KEY / MINIO_SECRET_KEY / MINIO_BUCKET: repo secrets for the deploy steps.
name: ci
on:
push:
branches: ['**']
tags: ['**']
schedule:
- cron: '19 4 * * *' # amweb-version-check
workflow_dispatch:
env:
ALPINE_VERSION: "3.24"
ALPINE_ARCH: "x86_64"
IMAGE_NAME: "alpine-kiosk"
PUBLIC_RELEASE_URL: "https://s3.jonasled.de/alamos-alpine-kiosk/"
PUBLIC_RELEASE_URL_BETA: "https://s3.jonasled.de/alamos-alpine-kiosk/beta/"
jobs:
build-image:
if: github.event_name != 'schedule'
runs-on: default
container:
image: alpine:3.24
steps:
# e2fsprogs: mke2fs -d builds slot.img from a directory. meson/ninja/build-base/pkgconf/glib-dev/
# openssl-dev: RAUC is compiled from source (no Alpine package). grub-bios: i386-pc modules for install-usb.sh.
# nodejs/git: needed by the JS actions in this alpine container; mc is the MinIO client for the deploy steps.
- name: Install packages
run: apk add --no-cache nodejs git bash squashfs-tools cpio coreutils findutils grub grub-efi grub-bios kmod curl e2fsprogs meson ninja build-base pkgconf glib-dev openssl-dev openssl
- uses: https://code.forgejo.org/actions/checkout@v7
- name: Build
env:
RAUC_SIGN_CERT: ${{ secrets.RAUC_SIGN_CERT }}
RAUC_SIGN_KEY: ${{ secrets.RAUC_SIGN_KEY }}
RUN_NUMBER: ${{ github.run_number }}
run: |
set -eu
# pipeline ids of the old GitLab project ended at 129021, keep versions growing
export KIOSK_VERSION=$((RUN_NUMBER + 129100))
if [ "$GITHUB_REF_TYPE" = branch ] && [ "$GITHUB_REF_NAME" = develop ]; then
export ARTIFACT_BASE_URL="$PUBLIC_RELEASE_URL_BETA"
else
export ARTIFACT_BASE_URL="$PUBLIC_RELEASE_URL"
fi
if [ -n "$RAUC_SIGN_CERT" ] && [ -n "$RAUC_SIGN_KEY" ]; then
umask 077
printf '%s\n' "$RAUC_SIGN_CERT" > "$RUNNER_TEMP/rauc.cert.pem"
printf '%s\n' "$RAUC_SIGN_KEY" > "$RUNNER_TEMP/rauc.key.pem"
export RAUC_CERT_PATH="$RUNNER_TEMP/rauc.cert.pem" RAUC_KEY_PATH="$RUNNER_TEMP/rauc.key.pem"
fi
bash build/build-image.sh
echo "Built version ${KIOSK_VERSION}"
ls -lh dist/
- uses: https://code.forgejo.org/forgejo/upload-artifact@v4
with:
name: alpine-kiosk-${{ github.run_number }}
path: |
dist/alpine-kiosk-*.tar.gz
dist/alpine-kiosk-*.raucb
dist/latest.json
retention-days: 30
- name: Deploy release (stable on default branch, beta on develop)
if: github.ref_type == 'branch' && (github.ref_name == github.event.repository.default_branch || github.ref_name == 'develop')
env:
MINIO_ENDPOINT: ${{ secrets.MINIO_ENDPOINT }}
MINIO_ACCESS_KEY: ${{ secrets.MINIO_ACCESS_KEY }}
MINIO_SECRET_KEY: ${{ secrets.MINIO_SECRET_KEY }}
MINIO_BUCKET: ${{ secrets.MINIO_BUCKET }}
DEFAULT_BRANCH: ${{ github.event.repository.default_branch }}
run: |
set -eu
curl -fsSL -o /usr/local/bin/mc https://dl.min.io/client/mc/release/linux-amd64/mc
chmod +x /usr/local/bin/mc
mc alias set minio "$MINIO_ENDPOINT" "$MINIO_ACCESS_KEY" "$MINIO_SECRET_KEY"
if [ "$GITHUB_REF_NAME" = develop ]; then
mc cp -r dist/ "minio/${MINIO_BUCKET}/beta/"
else
mc cp -r dist/ "minio/${MINIO_BUCKET}/"
fi
# Renovate bridge for the vendored AMweb.zip: the vendor only changes ETag headers, Renovate reads
# response bodies only. Republish the ETag as JSON on our bucket (see build/build-image.sh AMWEB_VERSION).
publish-amweb-version:
if: github.event_name == 'schedule'
runs-on: default
steps:
- name: Publish vendor ETag
env:
AMWEB_ZIP_URL: ${{ secrets.AMWEB_ZIP_URL }}
MINIO_ENDPOINT: ${{ secrets.MINIO_ENDPOINT }}
MINIO_ACCESS_KEY: ${{ secrets.MINIO_ACCESS_KEY }}
MINIO_SECRET_KEY: ${{ secrets.MINIO_SECRET_KEY }}
MINIO_BUCKET: ${{ secrets.MINIO_BUCKET }}
run: |
set -eu
ZIP_URL="${AMWEB_ZIP_URL:-https://files.alamos-gmbh.com/AMweb/AMweb.zip}"
ETAG=$(curl -fsSI "$ZIP_URL" | tr -d '\r' | awk -F': ' 'tolower($1)=="etag"{print $2}' | tr -d '"' | tail -1)
[ -n "$ETAG" ] || { echo "could not read ETag from $ZIP_URL"; exit 1; }
echo "vendor ETag: $ETAG"
mkdir -p amweb-version
printf '{"releases":[{"version":"%s"}]}\n' "$ETAG" > amweb-version/latest.json
cat amweb-version/latest.json
MC="$RUNNER_TEMP/mc"
curl -fsSL -o "$MC" https://dl.min.io/client/mc/release/linux-amd64/mc
chmod +x "$MC"
"$MC" alias set minio "$MINIO_ENDPOINT" "$MINIO_ACCESS_KEY" "$MINIO_SECRET_KEY"
"$MC" cp amweb-version/latest.json "minio/${MINIO_BUCKET}/amweb/latest.json"

View file

@ -1,169 +0,0 @@
# Builds the diskless Alpine kiosk image on a Kubernetes-executor GitLab
# Runner. No QEMU / virtualization is used or needed: build-image.sh only
# runs `apk --root`, mksquashfs and cpio/gzip -- all plain userspace
# operations for a native x86_64 target on an x86_64 runner. The one
# elevated capability required is CAP_SYS_CHROOT (used internally by apk
# to execute package post-install scripts), which is part of Docker's/
# Kubernetes' default capability set for containers running as root, so
# no `privileged: true` or extra `securityContext` is required from the
# runner's kubernetes executor config.
stages:
- build
- deploy
variables:
ALPINE_VERSION: "3.24"
ALPINE_ARCH: "x86_64"
IMAGE_NAME: "alpine-kiosk"
# Two update trains, published side by side in the same bucket:
# stable at the bucket root (unchanged -- kiosks already in the field
# point their UPDATE_URL here, see config/kiosk.conf.example) and beta
# under a "beta/" prefix, fed by the develop branch. Each is baked
# into its own latest.json's "url" field (via ARTIFACT_BASE_URL below)
# at build time, so it MUST match the prefix deploy-release-* actually
# publishes dist/ to (MINIO_BUCKET below) -- if these drift apart,
# kiosk-update.sh downloads whatever's at the stale URL (e.g. a
# GitLab login page, if this defaults back to a private job-artifact
# URL) and fails checksum verification, which is silent/confusing
# since the manifest itself still parses and looks valid.
PUBLIC_RELEASE_URL: "https://s3.jonasled.de/alamos-alpine-kiosk/"
PUBLIC_RELEASE_URL_BETA: "https://s3.jonasled.de/alamos-alpine-kiosk/beta/"
build-image:
stage: build
image: alpine:${ALPINE_VERSION}
tags:
- kubernetes
variables:
ARTIFACT_BASE_URL: "${PUBLIC_RELEASE_URL}"
# RAUC_SIGN_CERT/RAUC_SIGN_KEY: set these as protected "File" type
# CI/CD variables (Settings > CI/CD > Variables) holding the PEM
# contents of a cert/key pair generated ONCE, e.g.:
# openssl req -x509 -newkey rsa:4096 -nodes -keyout key.pem \
# -out cert.pem -days 3650 -subj /CN=alamos-alpine-kiosk
# GitLab writes each File variable's content to a runner-chosen
# temp path and exposes that path as the variable's own value --
# rebind those paths to the names build-image.sh actually reads
# (see ensure_rauc_keys()) below. Left unset here on purpose: without
# the two File variables configured, this job falls back to an
# ephemeral dev cert (loud warning, fine for testing this pipeline
# itself, but bundles built that way can't be installed on any
# device whose keyring trusts a different cert).
RAUC_CERT_PATH: "${RAUC_SIGN_CERT}"
RAUC_KEY_PATH: "${RAUC_SIGN_KEY}"
before_script:
# e2fsprogs: mke2fs -d builds slot.img directly from a directory (no
# loop-mount needed). meson/ninja/build-base/pkgconf/glib-dev/
# openssl-dev: compiling RAUC from source (Alpine has no rauc package
# at all -- main/community/edge all checked). grub-bios: i386-pc
# modules + grub-mkimage/grub-bios-setup, bundled into the release for
# install-usb.sh's BIOS boot install (replaces extlinux/syslinux).
- apk add --no-cache bash squashfs-tools cpio coreutils findutils grub grub-efi grub-bios kmod curl e2fsprogs meson ninja build-base pkgconf glib-dev openssl-dev openssl
script:
- export KIOSK_VERSION="${CI_PIPELINE_ID}"
- bash build/build-image.sh
- echo "Built version ${KIOSK_VERSION}"
- ls -lh dist/
artifacts:
name: "${IMAGE_NAME}-${CI_PIPELINE_ID}"
paths:
- dist/${IMAGE_NAME}-*.tar.gz
- dist/${IMAGE_NAME}-*.raucb
- dist/latest.json
expire_in: "30 days"
rules:
- if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
- if: '$CI_COMMIT_BRANCH == "develop"'
variables:
ARTIFACT_BASE_URL: "${PUBLIC_RELEASE_URL_BETA}"
- if: '$CI_PIPELINE_SOURCE == "push"'
.deploy-release-base:
stage: deploy
image:
name: minio/mc
entrypoint: [ '' ]
# MINIO_ENDPOINT/MINIO_ACCESS_KEY/MINIO_SECRET_KEY must be set as
# protected, masked CI/CD variables - never committed. Restrict these
# jobs to protected branch pipelines only (Settings > CI/CD >
# Protected branches) so the credentials are never exposed to forks/
# MRs.
needs:
- job: build-image
artifacts: true
before_script:
- mc alias set minio "${MINIO_ENDPOINT}" "${MINIO_ACCESS_KEY}" "${MINIO_SECRET_KEY}"
# Stable train: bucket root, unchanged from before so already-deployed
# kiosks' UPDATE_URL (config/kiosk.conf.example) keeps working as-is.
deploy-release-stable:
extends: .deploy-release-base
script:
- mc cp -r dist/ "minio/${MINIO_BUCKET}/"
rules:
- if: $CI_PIPELINE_SOURCE == "push" && $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
# Beta train: published under a "beta/" prefix in the same bucket, must
# match PUBLIC_RELEASE_URL_BETA above (baked into this build's
# latest.json by build-image's ARTIFACT_BASE_URL override for develop).
deploy-release-beta:
extends: .deploy-release-base
script:
- mc cp -r dist/ "minio/${MINIO_BUCKET}/beta/"
rules:
- if: $CI_PIPELINE_SOURCE == "push" && $CI_COMMIT_BRANCH == "develop"
# --- Renovate bridge for the vendored AMweb.zip -----------------------
# The vendor (files.alamos-gmbh.com) exposes no version-numbered
# filename and no JSON/HTML manifest -- the only thing that changes
# when they republish is the ETag/Last-Modified *headers* on the static
# AMweb.zip URL. Renovate's customDatasource only ever reads the HTTP
# response *body* (json/plain/yaml/toml/html; verified against
# https://docs.renovatebot.com/modules/datasource/custom/), so it can't
# poll the vendor URL directly. These two jobs bridge that gap: run on
# a schedule (create a GitLab "Pipeline Schedule" with a custom variable
# SCHEDULE_TASK=amweb-version-check -- Pipeline Schedules can't be
# defined from this file, only via the GitLab UI/API), they read the
# vendor's current ETag and republish it as a small JSON file on the
# same S3 bucket used for kiosk releases, in the exact shape Renovate's
# customDatasource expects. renovate.json then points there instead of
# at the vendor directly. See build/build-image.sh's AMWEB_VERSION pin
# for the other half of this (what Renovate actually edits).
check-amweb-version:
stage: build
image: alpine:${ALPINE_VERSION}
tags:
- kubernetes
rules:
- if: $CI_PIPELINE_SOURCE == "schedule" && $SCHEDULE_TASK == "amweb-version-check"
before_script:
- apk add --no-cache curl
script:
- |
ZIP_URL="${AMWEB_ZIP_URL:-https://files.alamos-gmbh.com/AMweb/AMweb.zip}"
ETAG=$(curl -fsSI "$ZIP_URL" | tr -d '\r' | awk -F': ' 'tolower($1)=="etag"{print $2}' | tr -d '"' | tail -1)
[ -n "$ETAG" ] || { echo "could not read ETag from $ZIP_URL"; exit 1; }
echo "vendor ETag: $ETAG"
mkdir -p amweb-version
printf '{"releases":[{"version":"%s"}]}\n' "$ETAG" > amweb-version/latest.json
cat amweb-version/latest.json
artifacts:
paths:
- amweb-version/latest.json
expire_in: "1 day"
publish-amweb-version:
stage: deploy
image:
name: minio/mc
entrypoint: [ '' ]
needs:
- job: check-amweb-version
artifacts: true
rules:
- if: $CI_PIPELINE_SOURCE == "schedule" && $SCHEDULE_TASK == "amweb-version-check"
before_script:
- mc alias set minio "${MINIO_ENDPOINT}" "${MINIO_ACCESS_KEY}" "${MINIO_SECRET_KEY}"
script:
- mc cp amweb-version/latest.json "minio/${MINIO_BUCKET}/amweb/latest.json"

150
README.md
View file

@ -94,7 +94,7 @@ prefers the other, previously-good slot on its own.
- `install/install-usb.sh` — formats a USB disk into the ESP, A/B slot
and data partition layout above, and installs a built release onto it,
bootable via real GRUB on both BIOS and UEFI.
- `.gitlab-ci.yml` — builds the image on a Kubernetes-executor runner.
- `.forgejo/workflows/ci.yml` — builds the image in an `alpine:3.24` container job.
## Building
@ -124,144 +124,12 @@ Output: `dist/alpine-kiosk-<KIOSK_VERSION>.tar.gz` (first-install
payload), `dist/alpine-kiosk-<KIOSK_VERSION>.raucb` (signed update
bundle) and `dist/latest.json`.
## GitLab CI
## CI
`.gitlab-ci.yml` runs the build in the `alpine:3.24` image on a runner
tagged `kubernetes`, using `CI_PIPELINE_ID` as the version. No
`privileged: true` or special `securityContext` is required — adjust the
`tags:` to match your runner and, for production use, replace
`ARTIFACT_BASE_URL` (currently pointing at GitLab's job-artifact URL,
which requires auth for private projects and expires after 30 days)
with wherever you actually publish releases (object storage, a static
site, etc.) so devices' `UPDATE_URL` manifests resolve to a stable,
publicly reachable download, and set `RAUC_CERT_PATH`/`RAUC_KEY_PATH` as
protected CI/CD file variables pointing at a real, persistent signing
cert/key pair.
## Installing to a USB stick
```sh
sudo install/install-usb.sh /dev/sdX dist/alpine-kiosk-42.tar.gz [my-kiosk.conf]
```
This **wipes** `/dev/sdX`, creates the ESP + `ALPINEKIOSK_A` +
`ALPINEKIOSK_B` + `ALPINEDATA` layout described above (both slots seeded
with identical content so the disk boots either one immediately), and
installs real GRUB for both BIOS and UEFI using the `grub-mkimage`/
`grub-bios-setup`/`grub-editenv` binaries and i386-pc module set bundled
in the release tarball itself (under `tools/`) — no `grub` package
needed on the installer host. Requires `parted`, `mkfs.ext4`,
`mkfs.vfat`, `wipefs`, `dd`, `e2label` (Alpine: `e2fsprogs` +
`e2fsprogs-extra`, the latter is where `e2label` actually lives). If no
`kiosk.conf` is given and
the target doesn't already have one, the example template is installed
— edit it on the device before first boot (or mount the `ALPINEDATA`
partition from another machine).
## `kiosk.conf`
Lives at the root of the `ALPINEDATA` partition (symlinked to `/kiosk.conf`
at runtime). See `config/kiosk.conf.example` for the full set of options:
- `KIOSK_URL` — page Chromium opens fullscreen. Defaults to
`http://localhost/setup`, the bundled AMweb app's own setup page (see
"Bundled AMweb app" below).
- `HOSTNAME` — system hostname (defaults to `alpine-kiosk`).
- `SSH_PUBKEY` (`_2`, `_3`, ...) — authorized keys for `root` over SSH
(password auth is disabled).
- `ROOT_PASSWORD` — optional root password for local console/recovery-shell
login only; SSH root login always requires `SSH_PUBKEY` regardless
(`PermitRootLogin prohibit-password` is set at the image level and
ignores this). Leave blank to keep root locked entirely.
- `VNC_PASSWORD` — optional wayvnc password; empty means unauthenticated.
- `NET_MODE` (`ethernet`/`wifi`), `WIFI_SSID`, `WIFI_PSK`, `WIFI_IFACE`,
`ETH_IFACE`.
- `TIMEZONE` — IANA/tzdata zone name (e.g. `Europe/Berlin`); defaults to
`UTC` if unset or unrecognized.
- `NTP_SERVERS` — space-separated list of NTP servers/pools for time
sync (`chronyd`, always running); defaults to `pool.ntp.org` if unset.
- `AUTO_UPDATE`, `UPDATE_URL`, `UPDATE_INTERVAL_MINUTES` — periodic
check against a `latest.json` manifest (the same format
`build-image.sh` produces); if newer, downloads the `.raucb` bundle
and hands it to `rauc install`, which verifies its signature and
writes it into the *inactive* slot (see "Updating and rollback"
above) — the currently running slot is never touched.
- `AUTO_REBOOT` — reboot automatically once an update is applied.
Applied at boot by the `kiosk` OpenRC service
(`kiosk-apply-config.sh`), which runs before networking/sshd/wayvnc.
## Bundled AMweb app
`build-image.sh`'s `bundle_amweb()` downloads
`https://files.alamos-gmbh.com/AMweb/AMweb.zip` at build time and
bundles its `dist/alarmmonitor-web` contents into `/var/www/amweb`
(override the source with `AMWEB_ZIP_URL`). It's served locally,
loopback-only, by a standalone `nginx` instance (`etc/nginx/amweb.conf`
and `etc/init.d/amweb`, independent of Alpine's own default nginx
setup, which isn't used) on `127.0.0.1:80`, with `try_files` SPA fallback so
client-side routes like `/setup` return `index.html` instead of a 404.
AMweb's setup (entered once at `http://localhost/setup`) is saved by
the browser into Chrome's `localStorage`. Since the whole root
filesystem is a fresh RAM overlay every boot, `start-kiosk.sh` symlinks
just that one directory (`~/.config/chromium/Default/Local Storage`,
prepared and chowned as root by `kiosk-apply-config.sh`) onto the
`ALPINEDATA` partition, so setup survives a reboot — the rest of the Chrome profile
(cache, cookies, IndexedDB, ...) stays ephemeral.
## Known limitations / things to verify on real hardware
- The initramfs bundles the *entire* stock Alpine module set (not a
curated subset) precisely so no target hardware's storage/USB
controller gets silently missed -- this makes `initramfs-lts` large
(~100MiB+) and the whole release correspondingly bigger, trading image
size for not needing to debug missing-driver boot failures per board.
- `wayvnc` currently mirrors the compositor read-only from other
clients' perspective by default configuration; adjust
`wayvnc-wait.sh`/`kiosk-apply-config.sh` if you want remote input.
- Wi-Fi firmware isn't bundled (`linux-firmware` is large); add the
specific `linux-firmware-<chipset>` package to `PACKAGES` in
`build-image.sh` for your target adapter.
- `ROOTFS_SLOT_SIZE_MIB` (default 2048) fixes each RAUC slot partition's
size at install time, from the release tarball's own `slot.img` size —
if the built system grows past that (e.g. more `chromium-lang` locales,
`EXTRA_FIRMWARE_PKGS`), raise it and reinstall; existing devices
updated in the field can't grow their already-partitioned slots.
- BIOS boot now goes through this project's own bundling of
`grub-mkimage`/`grub-bios-setup` (see `bundle_grub_tools()` in
`build-image.sh`) rather than a `grub-install` most other projects
rely on, since the target device is known and `grub-install`'s own
device-detection isn't needed — verify it boots on real BIOS/CSM
hardware (and a spare disk/VM) before relying on it, the same way you
would any new bootloader integration.
- RAUC's GRUB slot-selection logic (`grub.cfg`'s `_TRY` counters, the
`rauc-mark-good` service) is this project's own implementation of the
documented `ORDER`/`<slot>_OK`/`<slot>_TRY` grubenv contract RAUC's
GRUB backend expects, not a copy of RAUC's own reference script —
test the rollback path deliberately (see the "Simulate a bad update"
step below) rather than assuming it's identical to other RAUC+GRUB
deployments you may have seen. Verified end-to-end in QEMU/OVMF (ESP
stub -> `ALPINEDATA` chainload -> menu -> slot boot attempt), which is
also how a real bug was caught and fixed here: GRUB script has no
`$((...))` arithmetic (that's bash, not GRUB's script grammar), which
silently corrupted the `_TRY`-incrementing `menuentry` blocks and
dropped straight to a `grub rescue`/`grub>` prompt with no visible
error -- if you ever need to touch `grub.cfg`'s generation again,
boot-test the change the same way rather than trusting it by reading.
## Testing an update / rollback
1. Build, then serve `dist/` locally (`python3 -m http.server` from
`dist/`) and point a test device's `UPDATE_URL` at
`http://<host>:8000/latest.json`.
2. Bump `KIOSK_VERSION` and rebuild; `kiosk-update.sh` (or
`/etc/periodic/15min/kiosk-update`) should download the new
`.raucb`, `rauc install` it into the inactive slot, and — with
`AUTO_REBOOT=true` — reboot into it. `rauc status` should show the
new slot active and, once `rauc-mark-good` has run, good.
3. To exercise rollback, corrupt the *inactive* slot after an install
but before rebooting into it (e.g. `dd if=/dev/zero of=/dev/disk/by-label/ALPINEKIOSK_B bs=1M count=8`
if `B` is inactive) and reboot: GRUB's menu should fall back to slot
`A` once `B`'s `_TRY` count is exceeded, rather than hanging on a
broken slot.
`.forgejo/workflows/ci.yml` runs the build in an `alpine:3.24` container job
(Forgejo Actions), using the run number plus 129100 as `KIOSK_VERSION` so
versions keep growing from the old GitLab pipeline ids. Repo secrets:
`RAUC_SIGN_CERT`/`RAUC_SIGN_KEY` (PEM of the persistent signing pair) and
`MINIO_ENDPOINT`/`MINIO_ACCESS_KEY`/`MINIO_SECRET_KEY`/`MINIO_BUCKET` for the
release upload (stable on the default branch, `beta/` on `develop`). A daily
schedule republishes the AMweb vendor ETag for Renovate.

View file

@ -4,7 +4,7 @@
"customManagers": [
{
"customType": "regex",
"description": "Bump the pinned AMweb vendor ETag when the vendor republishes AMweb.zip -- see build/build-image.sh's AMWEB_VERSION comment and .gitlab-ci.yml's check-amweb-version/publish-amweb-version jobs for why this indirection (via our own S3-hosted manifest) is needed instead of pointing straight at the vendor.",
"description": "Bump the pinned AMweb vendor ETag when the vendor republishes AMweb.zip -- see build/build-image.sh's AMWEB_VERSION comment and .forgejo/workflows/ci.yml's publish-amweb-version job for why this indirection (via our own S3-hosted manifest) is needed instead of pointing straight at the vendor.",
"managerFilePatterns": ["/^build/build-image\\.sh$/"],
"matchStrings": [
"# renovate: datasource=custom\\.amweb depName=amweb\\nAMWEB_VERSION=\"(?<currentValue>[^\"]+)\""