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

chadtmiller.com/hud

A remote MCP server that shows atproto records as interactive UI inside MCP Apps hosts

0
0

Release 0.3.0

Merged
Merged chadtmiller.com asked to merge into main from chadtmiller.com/hud:release/next

Releases HUD 0.3.0, from the 1 change files on main: its changelog is below. Once this lands, ask for release.yml at main to publish it.

release-pull.yml

What changes

HUD 0.3.0, as knope release --override-version 0.3.0 makes it from main at 636506570eca: every version knope.toml names from 0.2.0 to 0.3.0 (the crates, the web packages, hudkit's), the version's CHANGELOG.md section, and the change files removed.

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.

Why

Apps built on HUD get main's changes only from a release. A 0.x minor change bumps the minor here, where knope alone would bump the patch.

How it was checked

The build is left to CI.

Approved

This is the release pull release-pull.yml makes. It bumps 0.2.0 to 0.3.0 in Cargo.toml, the three hud* entries in Cargo.lock, the web packages and the cross-references between them, android/gradle.properties and Kit.swift. It adds the 0.3.0 section to CHANGELOG.md and deletes the one change file. Every file knope.toml lists is bumped, and the changelog text matches the change file. Taking 0.3.0 for a 0.x breaking change fits AGENTS.md.

I read the diff of every file except web/package-lock.json. That file is 6,255 lines. I judged it from the other files and from the knope.toml entries that bump it, so I didn't read it line by line.

One thing to look at, which I don't count against the pull:

  • knope rewrote the package.json files from tabs to 2-space indent and dropped the trailing newline. web/package-lock.json shows the same whole-file churn. It is noise, not a content change. If a format check covers these files, CI will show it. Otherwise it's harmless, but it will make later diffs of these files noisy.

The build is left to CI, as the body says. Let check and the other workflows pass before you ask for release.yml.

Merged as 8371b12