0.6.7

Changed

• The live regions of the copy button, the code editor's status line, the
  identifier, the top bar's search, the decision dock, the upload field and
  Your preferences' saved mark are <output> elements; the code box, the
  self-description, the document pane's raw text, a refusal's evidence and
  the decision dock are named <section> elements; the user menu's
  separator is an <hr>. Each keeps the role the ARIA attribute gave it,
  and draws as before. A console script or test that selected one by
  [role="status"], [role="region"] or [role="separator"] selects it by
  its element (#624).
• fui-unit and fui-nowrap keep their text whole from the stylesheet's
  utilities layer, which comes after every component rule, in place of
  !important, so a console's own unlayered rule can now override them. The
  menu sheet's title, the lockup's accent word and the phone's Keyboard tab
  hold by the cascade alone, and draw as before (#626).
• The pager's range, the filter's count, the countdown's set points, the
  topology's zoom level, the busy spinner and skeleton lines and the date
  pickers' status lines are <output> elements; the data table's,
  compare's, line diff's and root matrix's scroll boxes are named
  <section> elements, and the reading pane's <section> drops its
  redundant role; the action menu's and the filter menu's separators are
  <hr> elements. Each keeps its role and draws as before. A console
  script or test that selected one by [role="status"], [role="region"]
  or [role="separator"] selects it by its element, and
  scripts/checks/markup-rules.sh (M6) refuses a new such role unless a
  NOTE: beside it says why the element keeps it (#639).

Fixed

• The top bar's typeahead shows its unreadable-answer sentence for an OK
  reply it cannot read (a null answer, groups that is not a list, a
  group with no list of hits), where it said "The search did not answer
  (undefined)." or stopped at "Searching…" (#633).

Support period

Only the newest release is supported: there are no maintenance branches, no long-term-support line and no backports, and upgrading is free. Under the Cyber Resilience Act, Cadasto B.V. commits to keep publishing security fixes for at least five years after each release (Art 13(8)) and ships them only in the newest release (Art 13(10)). For this release that commitment runs until the end of November 2031 (Regulation (EU) 2024/2847 Art 13(19)); see SECURITY.md.