diff --git a/CHANGELOG.md b/CHANGELOG.md index 15c270a..6fcaeef 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,8 +1,10 @@ # Changelog -## 0.1.0-rc.1 — pending publication +## 0.1.0-rc.1 — 2026-10-16 -First release candidate; no published artifacts yet. +First [published release candidate](https://proxy.dandaedre.com/gitea/MadGobblins/fader_master/releases/tag/v0.1.0-rc.1). +All three x86-64 GNU/Linux executables are available individually and together +in a `.tgz` archive, with checksums. See the [build provenance](docs/releasing.md#published-rc-build). - Linux MIDI control of application, group and default-output volume through PulseAudio or pipewire-pulse, with MIDI learn, pickup and mute feedback. diff --git a/docs/releasing.md b/docs/releasing.md index ea57f27..728f8eb 100644 --- a/docs/releasing.md +++ b/docs/releasing.md @@ -41,14 +41,17 @@ rust_realease --version rust_realease --help ``` -The installed `0.1.3` rejects Cross `pre-build`; it cannot build this release. -Upstream `0.1.6-rc.2` documents support for native prerequisites, but has not -been installed or qualified here. Select a publisher supporting `pre-build` -and rerun all dry-run/packaging checks before publishing. See the +Use a publisher built from upstream commit `ed2ce6e` or a later release +containing its Cross `pre-build` fix. The prebuilt `0.1.6-rc.2` executable +tested here still rejected that option; its version string alone is not +sufficient. The RC was published using a temporary build of that exact fix. +Rerun all dry-run/packaging checks before publishing. See the [publisher guide](https://proxy.dandaedre.com/gitea/idle-org/rust_realease/src/branch/main/docs/advanced-usage.md). [Cross.toml](../Cross.toml) uses the `0.2.5` x86-64 GNU image and installs ALSA, -Pulse and udev development packages inside the build container. The pinned +Pulse and udev development packages inside the build container. That image's +ALSA library is too old for this application: use the digest-pinned override +under [Published RC build](#published-rc-build). The pinned Rust toolchain and Cargo.lock constrain Rust builds. The container tag and apt repositories are not digest/snapshot pinned, so bit-for-bit reproducibility and the minimum supported runtime glibc version are not yet established. @@ -147,3 +150,33 @@ 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. + +### Published RC build + +Published on 2026-10-16: [v0.1.0-rc.1](https://proxy.dandaedre.com/gitea/MadGobblins/fader_master/releases/tag/v0.1.0-rc.1), +marked prerelease, not draft. Source commit: +`50d3097ff69f0cd3ec0ef15a0b74aa51d9c07de6`. The existing remote tag was verified +and was not moved. User profile edits were excluded using a clean worktree. + +Publisher source commit: `ed2ce6e86cab274d8f1350701605a3d0c6e2ac34`, built +temporarily without replacing the globally installed publisher. Its native +pre-build regression test passed. The original Cross image reached linking +but lacked ALSA's `snd_seq_client_info_get_card`. The successful packaging and +publication commands used this explicit override without changing tagged code: + +```sh +export CROSS_TARGET_X86_64_UNKNOWN_LINUX_GNU_IMAGE=ghcr.io/cross-rs/x86_64-unknown-linux-gnu@sha256:5e4193b02eaf85b64ae1545ceb942f380284a9760c005a6d04805af5221ee669 +``` + +This image is Ubuntu 24.04 based; older Linux distributions are not qualified +for these artifacts. Recipient systems need the runtime libraries listed +above. Rust remained pinned to 1.88.0 with the tagged Cargo.lock. + +Authenticated preview and compile-only packaging passed. The archive contains +exactly the three executables; all four artifact checksums passed locally and +all three binaries ran `--help` successfully without audio side effects. +Publication uploaded those four artifacts plus `SHA256SUMS`. The publisher +downloaded and verified every asset anonymously, checked archive layout, and +completed an isolated cargo-binstall installation for x86-64 GNU/Linux. +The API confirmed `prerelease = true`, `draft = false` and the five assets. +No existing assets were replaced. Real hardware qualification remains pending. diff --git a/task.md b/task.md index b4c36f7..1dca921 100644 --- a/task.md +++ b/task.md @@ -513,11 +513,12 @@ Dependencies: all required feature milestones; hardware-only ALSA remains an exp empty profiles by offering a safe Master-output fader. - [ ] **M12.4 Release gates:** all workspace/default/feature/MSRV checks, reproducible lockfile, license review and dependency advisory review using maintained tooling selected at implementation time. Measure/control latency under multi-surface load and publish the tested envelope. Release wrapper, offline contract tests, binstall metadata and an explicit - 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. + x86-64 GNU/Linux artifact configuration are prepared. The first release + candidate `v0.1.0-rc.1` is published; authenticated preview, Cross packaging, + archive/checksum checks and public cargo-binstall verification passed with + the publisher fix and image override recorded in [release preparation](docs/releasing.md). + Remaining reliability, hardware, advisory/license and reproducibility + qualification still blocks completion of this milestone. ## User requirement coverage