release(M12.4): mark 0.1.0-rc.1 candidate
Rust CI fader_master passed its selected CI mode.
MadGobblins/fader_master/pipeline/head This commit looks good Details

Update inherited package versions, lockfile, changelog and release contract. Make the real-workspace wrapper test cover either stable or prerelease versions.

Validation: eight wrapper tests, shell syntax, diff checks, workspace all-feature check/tests/doc tests, fmt, strict Clippy and release build passed. Default, no-default, portable and individual MIDI/Pulse checks passed. Real audio tests remain opt-in. Publication blocked by missing supplied token file and rust_realease 0.1.3 pre-build incompatibility; no artifacts uploaded.
This commit is contained in:
Dandaedre 2026-10-16 20:00:42 +02:00
parent ff84f167ab
commit 50d3097ff6
Signed by: Dandaedre
GPG Key ID: 440C6592E8A26D99
6 changed files with 37 additions and 17 deletions

View File

@ -1,8 +1,8 @@
# Changelog
## 0.1.0 — pending release
## 0.1.0-rc.1 — pending publication
Initial release preparation; no release date or published artifacts yet.
First release candidate; no published artifacts yet.
- Linux MIDI control of application, group and default-output volume through
PulseAudio or pipewire-pulse, with MIDI learn, pickup and mute feedback.

12
Cargo.lock generated
View File

@ -400,7 +400,7 @@ dependencies = [
[[package]]
name = "fader-config"
version = "0.1.0"
version = "0.1.0-rc.1"
dependencies = [
"fader-core",
"rustix 1.1.5",
@ -413,7 +413,7 @@ dependencies = [
[[package]]
name = "fader-core"
version = "0.1.0"
version = "0.1.0-rc.1"
dependencies = [
"proptest",
"regex",
@ -422,7 +422,7 @@ dependencies = [
[[package]]
name = "fader_master"
version = "0.1.0"
version = "0.1.0-rc.1"
dependencies = [
"anyhow",
"clap",
@ -792,7 +792,7 @@ checksum = "cf8baf1c55e62ffcace7a9f06f4bd9cd3f0c4beb022d3b367256b91b87513d98"
[[package]]
name = "midi"
version = "0.1.0"
version = "0.1.0-rc.1"
dependencies = [
"alsa",
"fader-core",
@ -1448,7 +1448,7 @@ checksum = "5d99f8c9a7727884afe522e9bd5edbfc91a3312b36a77b5fb8926e4c31a41801"
[[package]]
name = "tui"
version = "0.1.0"
version = "0.1.0-rc.1"
dependencies = [
"fader-core",
"ratatui",
@ -1515,7 +1515,7 @@ checksum = "06abde3611657adf66d383f00b093d7faecc7fa57071cce2578660c9f1010821"
[[package]]
name = "volume_lib"
version = "0.1.0"
version = "0.1.0-rc.1"
dependencies = [
"fader-core",
"libpulse-binding",

View File

@ -3,7 +3,7 @@ members = ["config", "core", "fader_master", "midi", "sound", "tui"]
resolver = "3"
[workspace.package]
version = "0.1.0"
version = "0.1.0-rc.1"
edition = "2024"
rust-version = "1.88"
license-file = "LICENSE"

View File

@ -8,17 +8,17 @@ integration does not create tags, push commits, or publish assets.
- Package: `fader_master`, with binaries `fader_master`,
`fader_master_client`, and `fader_master_server` (all included together).
- Version: inherited from `[workspace.package].version` in the root manifest;
currently `0.1.0`, expected tag `v0.1.0`. Keep [CHANGELOG](../CHANGELOG.md)
currently `0.1.0-rc.1`, expected tag `v0.1.0-rc.1`. Keep [CHANGELOG](../CHANGELOG.md)
aligned when changing the version. No independent script version constant.
- Target: `x86_64-unknown-linux-gnu`, release profile, locked dependencies.
This initial target deliberately excludes Windows and musl: the application
uses Linux ALSA, libudev, libpulse and Unix sockets. ARM is not yet qualified.
- Artifacts: both `.tgz` archives and standalone binaries, plus `SHA256SUMS`.
Archive: `fader_master-x86_64-unknown-linux-gnu-v0.1.0.tgz`, containing
Archive: `fader_master-x86_64-unknown-linux-gnu-v0.1.0-rc.1.tgz`, containing
a directory of the same stem with all three executables. Raw names are
`<binary>-x86_64-unknown-linux-gnu-v0.1.0`.
`<binary>-x86_64-unknown-linux-gnu-v0.1.0-rc.1`.
- Public Gitea repository: [MadGobblins/fader_master](https://proxy.dandaedre.com/gitea/MadGobblins/fader_master).
Release URL: `https://proxy.dandaedre.com/gitea/MadGobblins/fader_master/releases/tag/v0.1.0`.
Release URL: `https://proxy.dandaedre.com/gitea/MadGobblins/fader_master/releases/tag/v0.1.0-rc.1`.
Development origin: `git@git.dandaedre.com:MadGobblins/fader_master.git`.
The exact mapping in [rust-release.toml](../rust-release.toml) directs the
publisher to HTTPS without rewriting Git's origin.
@ -99,13 +99,13 @@ rust_realease . --package fader_master --artifact-format both --compile-only
`shellcheck -s sh release.sh` when available. Tests use only fake tokens and
a fake publisher; they never contact Gitea.
4. Check the expected local and remote tag without changing either:
`git show-ref --verify refs/tags/v0.1.0` and
`git ls-remote --tags origin refs/tags/v0.1.0 'refs/tags/v0.1.0^{}'`.
`git show-ref --verify refs/tags/v0.1.0-rc.1` and
`git ls-remote --tags origin refs/tags/v0.1.0-rc.1 'refs/tags/v0.1.0-rc.1^{}'`.
Before publication both must resolve to the intended HEAD. Creating/pushing
the tag is a separate authorized step, not part of the wrapper.
5. Run the dry run with the real token file. It must report the contract above
and no metadata/prerequisite errors. Independently inspect the Gitea
`/api/v1/repos/MadGobblins/fader_master/releases/tags/v0.1.0` endpoint.
`/api/v1/repos/MadGobblins/fader_master/releases/tags/v0.1.0-rc.1` endpoint.
A confirmed 404 means absent only when the repository is accessible; do not
treat authentication/network/server failures as absence.
6. If a release exists, inspect draft/prerelease status and **all asset names**,
@ -138,3 +138,12 @@ the installed publisher rejecting `pre-build` and the absent tag. No real token
file was supplied, so authenticated wrapper verification remains outstanding.
Packaging/checksum/archive qualification is blocked by publisher compatibility.
No tool was upgraded and nothing was tagged, pushed or published.
### Release-candidate follow-up
The workspace and lockfile now identify `0.1.0-rc.1`; the wrapper automatically
marks it as a prerelease. The RC release API returned 404 and the remote RC tag
was absent at preparation time. Publication is pending: the supplied token
file was not found, and the installed publisher still needs upgrading for
Cross `pre-build` support. Existing local profile edits must stay out of the
release; use a clean checkout of the RC tag when packaging and publishing.

View File

@ -1,6 +1,7 @@
#!/usr/bin/env python3
"""Offline contract tests: never invoke the real publisher or use real tokens."""
import os
import json
from pathlib import Path
import shutil
import subprocess
@ -113,7 +114,15 @@ exit "$TEST_EXIT"
result = subprocess.run([str(ROOT / "release.sh"), str(self.token), "--dry-run"],
cwd=self.base, env=env, text=True, capture_output=True)
self.assertEqual(result.returncode, 0, result.stderr)
self.assertEqual(result.stdout, "<--dry-run>\n")
metadata = json.loads(subprocess.check_output(
["cargo", "metadata", "--offline", "--no-deps", "--format-version", "1"],
cwd=ROOT, text=True))
version = next(package["version"] for package in metadata["packages"]
if package["name"] == "fader_master")
expected = "<--dry-run>\n"
if "-" in version:
expected += "<--prerelease>\n"
self.assertEqual(result.stdout, expected)
self.assertNotIn("fixture-secret", result.stdout + result.stderr)

View File

@ -516,6 +516,8 @@ Dependencies: all required feature milestones; hardware-only ALSA remains an exp
x86-64 GNU/Linux artifact configuration are prepared. Publisher compatibility,
authenticated dry run, Cross artifact qualification and the remaining release
criteria are still outstanding; see [release preparation](docs/releasing.md).
The first release candidate is version `0.1.0-rc.1` (tag `v0.1.0-rc.1`).
Publication remains pending a readable token file and compatible publisher.
## User requirement coverage