CI: Only publish releases into the Debian stable component #1680

Merged
Jade merged 2 commits from spaetz/continuwuity:stable_deb into main 2026-04-17 20:13:45 +00:00

2 commits

Author SHA1 Message Date
deba5673bc docs: Describe Debian components
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m25s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 8m2s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 34s
Describe "stable", "stable unstable" and "dev" components
2026-04-17 15:58:22 +02:00
af44ae012c CI: Only publish releases into the Debian stable component
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 31s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m22s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 8m9s
Previously, we would push all tagged releases into the stable component,
including alphas and rc's. Let's use some regex to only push stable
releases which conform to tag "^v+\d\.+\d\.+\d$"
so we ONLY get the manually published releases into the stable
component.

All pre-releases go into the "unstable" component for now. Nightly builds
go into the "dev" component (as before) and feature branches still get
their dedicated component named after the branch.

TODO: It would be nifty if stable releases would ALSO be published at the
unstable component.
2026-04-17 15:37:31 +02:00