chadtmiller.com/knotless

Switch repository

Loading…

What changes

web/ pins @atproto/lex at 0.4.4, up from 0.3.14, and its lockfile follows. The lex script (lex build --lexicons .lexicons --out src/lib/lexicons --clear --import-ext .ts) and the way pages call XRPC are unchanged.

Why

grain's web is moving onto the same setup as knotless's, at 0.4.4, and the two should stay on one version. 0.4 changes nothing lex build writes: its minor change is to lex install (a v2 manifest with local resolvers, which knotless does not use), and @atproto/lex-client 0.4.0 moves its internals onto a new @atproto/lex-rpc package while re-exporting everything, so it stays backwards compatible. It also validates rkey on record operations and adds rkeyFor / rkeyForCreate. 0.4.1 to 0.4.4 are dependency patches.

How it was checked

The lockfile was updated with npm install --package-lock-only. Building the lexicons, svelte-check, the pages and their shots are left to the web, shots and e2e checks.

Shortcomings

Nothing was built or run locally.

🤖 Generated with Claude Code

This bumps @atproto/lex in web/ from 0.3.14 to 0.4.4 and regenerates the lockfile. The diff is only web/package.json and web/package-lock.json.

The lockfile changes match what the description says. lex-client 0.4.0 now depends on the new lex-rpc. lex-installer 0.2.x pulls in the handle and did resolvers, prettier and undici. Those are transitive dev dependencies of lex install, which this repo doesn't use. The lex build script is unchanged.

I couldn't confirm that the build works. The web, check, shots and e2e runs were all still queued when I looked, and nothing was run locally. npm run check runs lex build, so it is the run that matters here. Wait for it to pass before merging. If the generated src/lib/lexicons output differs under 0.4.4, that run is where it would fail.