~ knotless Search/
↑↓ move↵ open⇧↵ all results

grain.social/grain

photography-focused photo sharing platform

grain.social
1 collaborator
0
2

docs: AGENTS.md says HUD 0.3.0 and what the app file's kits.oldest is

Merged chadtmiller.com asked to merge into feature/hud from grain.social/grain:next/hud-0.3.0-docs

Only what this pull adds. It is built on The next grain.social and grain-ios, drawn by HUD.

.knotless/workflows/next.yml+1−1
@@ -7,7 +7,7 @@
#
# `hud check` is HUD's own loader, as hud-next runs it at startup: the hud
# binary is built from HUD's public repository at the tag of the version
# the app file names (`"hud": ">=0.2.0"`: v0.2.0), the version
# the app file names (`"hud": ">=0.3.0"`: v0.3.0), the version
# `just hud-version` sets with the packages', and kept in /opt/hud, so it
# is built again only when that version moves; its build (Rust, and HUD's
# pages, which it embeds) is deleted once the binary is out of it.
AGENTS.md+10−5
@@ -255,7 +255,7 @@ them: `just hud <HUD checkout>` runs `HUD_APPS=$PWD/next HUD_PORT=8787
cargo run -p hud -- serve` in that checkout; restart it after editing a
view.
The app file says the HUD it needs (`"hud": ">=0.2.0"`): an older HUD
The app file says the HUD it needs (`"hud": ">=0.3.0"`): an older HUD
refuses it with that message alone. So hud-next is deployed with a HUD
that has what a change here uses before the change deploys; a view using
a prop the deployed HUD may lack writes it `?prop`, which an older HUD
@@ -264,9 +264,14 @@ drops with a warning. `next/lexicons/social/grain` is a copy of
serves them with in place of any it bundles, so a HUD that drops or
changes a bundled Grain lexicon cannot refuse the app; `check-apps.mjs`
fails when the copy differs: copy it over after changing a lexicon. The
app file and views name HUD's JSON Schemas (`$schema`) at a35a6d8, the
first HUD with them (`main`'s once HUD's app/shell lands there), for an
editor's completion.
app file and views name HUD's JSON Schemas (`$schema`) at the tag of that
version (`v0.3.0`), for an editor's completion.
The app file's `"kits": {"oldest": …}` is the oldest HUD kit an app build
Grain still serves carries (builds that send no version count as 0.2.0):
`hud check` warns where a view uses a component or prop newer than it with
no `{"$kit": …}` gate or `fallback` around it. Raise it as old builds age
out, beside `web/static/app-version.json`'s minimums.
A push to `feature/hud` touching `next/` deploys it to
`https://next.grain.social` (`next-deploy.yml`, through
@@ -301,7 +306,7 @@ the build bundles them all and the image needs no `node_modules`.
The `next` check (`.knotless/workflows/next.yml`) runs `HUD_WORKSPACE=off
hud check next`, with a `hud` built from HUD's tag of the version the app
file names (`"hud": ">=0.2.0"`: `v0.2.0`) and kept between runs, then
file names (`"hud": ">=0.3.0"`: `v0.3.0`) and kept between runs, then
`next/check-apps.mjs` (Grain's own rules: view names, links, permission
sets, the lexicons' copy), then svelte-check and the SvelteKit build, on a
pull touching `next/` or `lexicons/social/grain`; the `next-image` check