| Filename | Latest commit message | Latest commit date |
|---|---|---|
Sebastian Spaeth
b4a2a457a1
Some checks failed
Documentation / Build and Deploy Documentation (push) Has been cancelled
Checks / Prek / Pre-commit & Formatting (push) Has been cancelled
Checks / Prek / Check changed files (push) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (push) Has been cancelled
Release Docker Image / Build linux-amd64 (release) (push) Has been cancelled
Release Docker Image / Build linux-arm64 (release) (push) Has been cancelled
Release Docker Image / Create Multi-arch Release Manifest (push) Has been cancelled
Release Docker Image / Build linux-amd64 (max-perf) (push) Has been cancelled
Release Docker Image / Build linux-arm64 (max-perf) (push) Has been cancelled
Release Docker Image / Create Max-Perf Manifest (push) Has been cancelled
Release Docker Image / Release Binaries (push) Has been cancelled
Release Docker Image / Mirror Images (push) Has been cancelled
Right now our weekly Debian versioning scheme is VERSION="$BASE_VERSION~git$DATE.$SHA-$CLEAN_COMPONENT". This sorts weekly releases AFTER the BASE_VERSION, so when both stable and unstable are enabled, we never get weekly versions installed. https://wiki.debian.org/Versioning proposes {upcoming_version}~git{date}.{hash}-{revision} for nightly releases, which means we would have to know the release number of the upcoming version in advance. I don't think that is useful for us. By switching from a tilde to a dash, our weekly versions are not sorted above the stable base version and we will install the weekly versions over the base version, which I believe is closer to what we intend. Fixes: #2081 |
||
| .. | ||
| auto-labeler.yml | ||
| build-debian.yml | ||
| build-nix.yml | ||
| check-changelog.yml | ||
| documentation.yml | ||
| mirror-images.yml | ||
| prek-checks.yml | ||
| release-image.yml | ||
| renovate.yml | ||
| update-flake-hashes.yml | ||