# [0.4.0](https://gitea.psi.ch/mx/aare_launcher/compare/v0.3.0...v0.4.0) (2026-07-27) ### Bug Fixes * add missing releaserc ([2027bb3](2027bb3589)) ### Features * semantic release workflow ([e7a4d3c](e7a4d3caf8))
aare_launcher
CLI/TUI launcher for the AareDAQ server and GUI on MX beamline consoles at PSI.
Installed as the aarel command. It detects the current beamline and launches the
matching application, opens a TUI to pick one, or deploys a new checkout.
Usage
aarel pick # open the TUI to choose what to launch
aarel gui # launch the GUI for the detected beamline
aarel server # launch the server for the detected beamline
Each command has a single-letter alias (p, g, s). --config <path>
selects a different config file; it defaults to data/defaults.json.
Launching
gui and server pick their config entry from the detected beamline. Use
--entry <name> to launch a different one.
Development
cargo build # build
cargo test # run the tests
cargo fmt --all # format
cargo clippy --all-targets --all-features -- -D warnings # lint
Releases are automated with semantic-release: merging a PR to main derives
the next version from the commit history, bumps Cargo.toml, tags the release
and builds the RPM.
Commit messages must follow Conventional Commits. The release version and notes are generated from them, so a commit that isn't
feat:,fix:, etc. produces no release. Usefeat:for a minor bump,fix:for a patch, and afeat!:/fix!:(or aBREAKING CHANGE:footer) for a major bump.