# Releasing LiosBar
Releases are source-controlled in the private
`Tknott95/LiosBar` GitHub repository and published publicly as the
`lios-bar` crate.
From a clean checkout with GTK4/VTE development packages installed:
```sh
cargo fmt --all -- --check
cargo clippy --no-default-features --all-targets -- -D warnings
cargo clippy --no-default-features --features widget --all-targets -- -D warnings
cargo clippy --all-targets -- -D warnings
XDG_RUNTIME_DIR=/tmp cargo test --no-default-features --all-targets
XDG_RUNTIME_DIR=/tmp cargo test --all-targets
xvfb-run -a env GSK_RENDERER=cairo G_DEBUG=fatal-criticals cargo test --all-targets -- --ignored --test-threads=1
cargo doc --no-default-features --no-deps
sh audit-package.sh
cargo package
cargo publish --dry-run
git status --short
```
Confirm that `Cargo.toml`, `Cargo.lock`, `CHANGELOG.md`, `--version`, and the
release heading agree. Commit and push the exact source state, publish with
`cargo publish`, then verify the new version through the crates.io API and
`cargo info lios-bar@VERSION --registry crates-io`.
Never publish with uncommitted files, skipped Clippy warnings, absent license
or notice files, or a package archive whose contents were not reviewed.
Review both the standalone and widget-only feature sets. The latter must not
depend on VTE or start a shell. Publish this crate before a host adds a released
dependency on its new API; a local path dependency alone is not publishable.