# Changelog What changed in each version of HUD for the apps built on it: the server, the web packages (`@hud/renderer`, `@hud/shell`, `@hud/shared`), HUDKit for iOS and hudkit for Android, which share one version. Written from the change files in `.changeset/` (see `knope.toml`). ## 0.3.1 (2026-11-22) ### Fixes #### A Covers' bar shows while picking in Panes Picking covers in a `Panes` (Select in its row, as Grain's profile has it), the bar with Cancel, how many and the action now stays at the bottom of the screen, above the shell's tabs, at every width. Before, it was held to the bottom of the strip of panes, after the last cover and often off the screen. While picking, the strip shows only the pane in use and doesn't scroll; Cancel or the action finishing brings it back to that pane. #### A feed in the web shell pages as it is scrolled A screen with a `next` loads its next page itself as its foot comes within a screen of view, as HUDKit's and the Android kit's lists do: one page at a time, on the screen in front alone, stopping at an error until Try again, and never where the browser asks to save data. Its Load more button stays, for the keyboard, screen readers and pages drawn with no script. `LoadMore` takes `auto` for a host to page so. #### A record with no facets has its links, mentions and tags found A `RichText` with `format: "facets"` whose `facets` read nothing, as a record another client wrote with none at all, has its links, @mentions and #tags found as `format: "detect"` finds them, as Grain's web and iOS apps do. Facets given, an empty list too, are drawn as they are, and an embedded Bluesky post keeps its own. ## 0.3.0 (2026-11-22) ### Breaking Changes #### Old builds of an app draw what they can of newer views HUDKit, hudkit and the web shell say their version as they call HUD (the `place.hud/kit` client capability, and `callTool`'s `kit`), and HUD fits each tree to the kit drawing it: a client that says none is drawn for the oldest kit, 0.2.0. A view may gate a Stack, Pane or Bar on it, `"when": {"$kit": ">=0.3.0"}` or `"unless"`, and give any node a `fallback`: a component newer than the kit is sent as its children, else its fallback, else nothing. A release build of HUDKit, hudkit or the web renderer draws a component it doesn't know the same way, where a debug build still shows it isn't drawn yet. An app file's `"kits": {"oldest": "0.2.0"}` makes `hud check` warn where a view uses a component or prop newer than that with nothing around it for older kits. ## 0.2.0 ### Features #### HUD's SDK, published as versioned packages An app is built on HUD from published packages instead of a copy of HUD's source. On the web, `@hud/renderer`, `@hud/shell` and `@hud/shared` come from HUD's npm registry on knotless, built with `svelte-package`: Svelte components with their types, Svelte as a peer dependency. `@hud/shared` holds `result.ts` and `interactions.ts`, so `import type { Call } from '@hud/shared/result'` takes the place of an alias to HUD's `web/shared`. On iOS, HUDKit is `hud.HUDKit` in HUD's Swift package registry. On Android, hudkit is `place.hud:hudkit` in HUD's Maven repository, with its POM and Gradle module metadata, and it brings MapLibre Native's OpenGL ES build itself, so an app needs no dependency substitution of its own. docs/sdk.md says how an app takes each. #### One version for HUD The server and every package share one version, starting at 0.2.0: the server's is the crates', and each package's is the same number. A change an app built on HUD sees adds a change file (`knope document-change`), and a release bumps every package together. #### `hud check` names every problem of an app's directory `hud check ` loads a directory of apps exactly as `hud serve` loads `HUD_APPS` (`HUD_WORKSPACE=off` to check apps served alone), printing every problem on its own line as `file: path: what` and exiting 1 on any. `hud serve` names every problem too as it refuses to start. Run it in an app's checks, with the HUD you deploy against. #### An app file's `hud`: the HUD versions it runs on `"hud": ">=0.2.0"` (a semver requirement) in an app file makes an older HUD refuse the app with that alone (`app.hud: the app needs HUD >=0.2.0, and this HUD is …`). A HUD that meets it checks the rest. #### Optional keys in views A view's key written `?key` is read as `key` where HUD knows it, and left out with a warning where HUD finds a problem in it (a prop, a value or a key it doesn't know), so a view written for a newer HUD runs on an older one. Any other unknown key is still refused. #### An app's own lexicons An app may ship the lexicons its views and push call in `lexicons/` beside its views, at any depth. HUD checks the views against them and reads them as it serves, in place of a bundled lexicon of the same NSID, so it never refuses an app over a lexicon it doesn't bundle. #### JSON Schemas of an app file and a view `schemas/json/app.json` and `schemas/json/view.json` (also `hud schema app|view`) describe an app file and a view for an editor's completion and checks. Name `https://knotless.dev/chadtmiller.com/hud/raw/v0.2.0/schemas/json/view.json` in a view's `$schema`, which a view may now hold.