v0.6.1

⚠️ Upgrading

• One migration, GitHistoryNewestCommit, applied at startup. Widening only: two nullable
  columns on sources, filled by the next pass over each history source.

Added

• A history source shows where its ref had got to. Each pass records the newest commit
  it found, and the source's row reads newest 9d2ef06, 3d ago, with the full sha and date
  on hover; SourceSummary.newestCommit carries both. A source following HEAD in a
  checkout whose local branch nobody pulled indexed the same 174 commits for three days
  while origin/main gained 52, with every count on screen correct and nothing to say the
  history had stopped. It records where the ref points, not how far indexing got, which
  the counts and the source's state report. An inventory that fails leaves the last
  record; one whose settings select no commits clears it.

• A history source's settings can be edited. Its row had no editor, so changing the
  ref meant the API, or removing the source and re-reading every commit. The editor holds
  the ref, the message, stat and diff with its cap, merges, a commit limit, a date and the
  include paths, and the add dialog now shows the same fields from the same component, so
  a ref such as origin/main can be chosen when the source is added. The editor says
  which kind of change it is about to save: the ref, limit, date and merges choose which
  commits are indexed and keep the documents already there, while the message, stat, diff
  and paths change every document and re-read the history.

Changed

• History settings git cannot be asked with are refused when a source is added or
  edited. A malformed ref, a commit limit below one or a diff cap past the read ceiling
  was stored as sent, answered 200, and found on the next pass as the source being
  unavailable. It is now a 400 carrying the same reason the inventory gives, and the
  add and edit dialogs show it, staying open. None of the checks runs git; a well-formed ref that names
  nothing still shows on the corpus after the refresh.

Fixed

• A dialog shows its own failures. Eleven dialogs sent a failure to the page's error
  banner, which sits under the dialog's overlay and inside the part of the page Radix
  hides from assistive tech, so a refused save left the dialog open with nothing in it to
  say why. Measured with New corpus and a name already taken: the 409's message rendered
  behind the overlay. The file and extracted-text viewers, on a load that failed, went on
  saying "Reading…" for ever. Each now shows the server's message at its top, scrolled
  into view if the dialog had scrolled past it, and stays open. A test that parses the
  source holds every dialog to it.

• A source at the workspace root has a name. Its path is empty, and rootPath ?? kind
  passed the empty string through, so the row showed no name and its buttons were
  labelled "Remove source " with nothing after it. It is now workspace root.

---

---

docker pull ghcr.io/merp4/dexicon:0.6.1

Digest sha256:84ec1e5a2fd010dfe390183152159516ee6db709ab03c5198e1c8d4ef867baae. An SBOM and build provenance are attached to the
image in the registry.