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

grain.social/grain

photography-focused photo sharing platform

grain.social
1 collaborator
0
2

next: HUD 0.3.0: the apps say their kit version, old builds get what they can draw

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

What changes

Grain moves to HUD 0.3.0 (just hud-version 0.3.0): @hud/renderer, @hud/shell, @hud/shared ^0.3.0, hud.HUDKit 0.3.0 and place.hud:hudkit 0.3.0. With it the web, iOS and Android clients say their kit version as they call HUD, and HUD draws each for its own kit: a component newer than an app build is sent as its children, its fallback, or nothing, so builds already on phones never show "isn't drawn yet".

The app file says "kits": {"oldest": "0.2.0"}, the oldest app build Grain still serves, so hud check warns where a view uses a component or prop newer than 0.2.0 with no {"$kit": …} gate or fallback around it. It is raised as old builds age out, beside app-version.json's minimums. Its "hud" is >=0.3.0, so the next check builds hud check from v0.3.0. The app file's and views' $schema point at HUD's v0.3.0 schemas, which know kits.

Why

A view change reaches every client at once, but an app build keeps the renderer it shipped with; until now HUD could not tell them apart, and an unknown component drew a developer placeholder.

How it was checked

  • HUD 0.3.0 runs on next.grain.social already (hud-next at main 8371b12), loading the live apps ("1 app and 17 views, as HUD 0.3.0 loads them").
  • node next/check-apps.mjs; npm run check in next/ (0 errors).
  • swift package resolve fetched hud.HUDKit 0.3.0 from the registry.
  • The v0.3.0 schemas resolve and know kits.

Shortcomings

Nothing in HUD's catalog is newer than 0.2.0 yet, so the per-kit replacement and the warnings first act on the next new component. Kit gates are on Stack, Pane and Bar alone. The iOS and Android builds were not run locally beyond resolving the package; the android check builds Android.

Approved

This moves Grain to HUD 0.3.0 in all the places AGENTS.md says to bump: next/package.json and its lock, ios/HUD/Package.swift and ios/Package.resolved, android/gradle/libs.versions.toml, and the app file's hud. It adds kits.oldest: "0.2.0" and points the $schema URLs at HUD's v0.3.0 tag. The diff matches what the body says, and the lock entries all move together to 0.3.0.

I found nothing that must change. The next, android, next-image and test checks were still running when I looked, so the approval doesn't rest on them. The iOS build wasn't run, as the body admits; the package pin and Package.resolved agree.

Optional follow-up, not a reason to hold the pull: some docs still describe the old state.

  • AGENTS.md (around lines 258 and 304) quotes "hud": ">=0.2.0" and v0.2.0.
  • .knotless/workflows/next.yml:10 has the same comment.
  • AGENTS.md says the $schema URLs point at a35a6d8, and they now point at v0.3.0.

AGENTS.md could also name kits.oldest, which is raised alongside app-version.json's minimums.

Merged as 5e7fb44
Part of a stack of 2
  1. next: HUD 0.3.0: the apps say their kit version, old builds get what they can draw Landed as 5e7fb44
  2. main