luxe update and /update, editable question answers, and a version bump owed once per release

- 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.
This commit is contained in:
Evan Whittaker
2026-10-17 14:14:27 -05:00
parent 0e84deb59c
commit bf86df5098
41 changed files with 794 additions and 355 deletions

View File

@@ -283,12 +283,15 @@ cd web && npm run deploy # needs `wrangler login` once
## Versioning
One version for the whole workspace (`[workspace.package]` in `Cargo.toml`), following semver. A
pull request to the public repository that changes what ships (`crates/`, `Cargo.toml`,
`Cargo.lock`) bumps it by exactly one step, updates the internal path-dependency pins to match, and
adds a `## [x.y.z]` section to `CHANGELOG.md`. The `Version` workflow runs
`scripts/version-check.py` against the target branch to hold it to that; changes to the site, the
guide or CI owe no bump.
One version for the whole workspace (`[workspace.package]` in `Cargo.toml`), following semver, and
the version on `main` is always the next release. The first pull request to the public repository
that changes what ships (`crates/`, `Cargo.toml`, `Cargo.lock`) after a release, which is when a
`v<version>` tag marks the current one, bumps it by exactly one step, updates the internal
path-dependency pins to match, and adds a `## [x.y.z]` section to `CHANGELOG.md`. Later pull
requests before the next release owe no bump and add their entries to that section; one that
breaks something may still move a pending patch to a minor, one step past the last release. The
`Version` workflow runs `scripts/version-check.py` against the target branch to hold it to that;
changes to the site, the guide or CI owe nothing.
```bash
python3 scripts/version-check.py origin/main # what the pull request check runs