Skip to content

v0.0.1a2

@tony tony tagged this 05 Apr 23:39
why: The next pre-release needs all published workspace packages and internal pins to move in lockstep.
what:
- bump the workspace and package versions from 0.0.1a1 to 0.0.1a2
- update internal package pins, release tooling, and release docs to the new version
- refresh tests and uv.lock so workspace metadata matches the new release target
Assets 2
Loading