Why:
Daily stable archives need native ARM packages alongside x86 packages.
Impact:
All current daily package workflows build, publish, and install-test ARM.
Before:
The package archives contained only amd64 or x86_64 binaries.
After:
Archives contain native arm64 or aarch64 binaries with signed metadata.
Technical Overview:
Add native GitHub ARM runners to every current daily package matrix.
Publish both architectures in one serialized repository update.
Keep immutable snapshots separated by architecture.
Filter APT indexes by architecture and advertise both architectures.
Make EL Mock validation accept the requested RPM architecture.
Verify each published package in a matching native distro container.
With the help of AI-Agents: Codex
Why:
Scheduled daily-package workflows read their enable switches before entering the protected publishing environment. Six switches were configured only on that environment, so scheduled jobs saw an empty value and silently skipped while reporting success.
Impact:
All seven daily-package schedules now use one repository-level switch model. Missing or malformed switches fail preflight and reach the existing scheduled failure-issue job instead of creating a false green run.
Before:
An unset schedule switch was treated as false, making a configuration mistake indistinguishable from an intentional disable.
After:
Each schedule accepts only true or false. True builds and publishes, false intentionally disables the schedule, and every other value fails with a variable-specific error. Documentation separates repository switches from protected archive configuration.
Technical Overview:
Apply the same case-based schedule guard to Debian 13, Ubuntu 26.04, EL10, Alpine 3.24, Amazon Linux 2023, Fedora 44, and openSUSE Leap 16.0.
With the help of AI-Agents: Codex
Why:
Broaden daily-stable coverage to a musl-based mainstream distribution while preserving Alpine's native packaging policy.
Impact:
Maintainers can build, retain, publish, and verify signed Alpine 3.24 x86_64 packages from current rsyslog main.
Before/After:
Before: the shared archive automated APT and RPM families only.
After: it also supports an immutable, signed APK repository with clean-container installation verification.
Technical Overview:
Use Alpine's 3.24-stable rsyslog APKBUILD as the packaging baseline.
Generate ordered daily versions and signed APK packages plus an incremental APKINDEX.
Publish immutable packages and snapshots to the shared DigitalOcean Space.
Verify the exact published version in a clean Alpine 3.24 container.
Keep scheduling disabled until the first manual end-to-end publication succeeds.
Open or update an issue when a scheduled build, publish, or verification fails.
With the help of AI-Agents: Codex
