- luxe update and /update update Luxe with the command for however it was installed (cargo or Homebrew), run one program at a time with the terminal attached, then check that the luxe on PATH is the new version. Luxe never downloads or replaces its own binary. The start screen says "Update available · /update". - A question's typed answer edits at its caret: arrows, word jumps, Home, End and Delete work, and up and down move through a wrapped answer before leaving it. - The version check owes a bump once per release: the version on main is the next release, and only a released one (a v-tag) has to move. - Dependency updates arrive through the sync, so Dependabot and the weekly jobs no longer run here.
653 B
653 B
Changelog
Every release of Luxe, newest first. The format follows Keep a Changelog,
and versions follow Semantic Versioning. While Luxe is below
1.0, a minor bump (0.x.0) may break config, flags or the --rpc protocol, and a patch bump never
does.
The version on main is always the next release. The first change to what ships (crates/,
Cargo.toml, Cargo.lock) after a release bumps it one step and opens its section here, and later
changes add to that section until it ships; scripts/version-check.py holds them to it.
[0.1.0]
The first public release.