chore(release): prepare v0.2.1 #5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "release-v0.2.1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bumps
Cargo.tomlto 0.2.1 so thev0.2.1tag publishes an image that reports its own version correctly.The release smoke sets
EXPECTED_VERSIONfromCargo.toml, not fromGITHUB_REF, so a tag pushed on 0.2.0 would shipforge.oddie.app/jlxq0/typst-mcp:v0.2.1containing a binary that answers0.2.0on/api/v1/version— and every gate would pass. Same shape as the fixture we fixed on #3: a check that cannot fail on the thing it appears to be checking. Bumping first is whatac04dacdid for v0.2.0.Carries #3, the RFC 8252 §7.3 loopback redirect fix.
Gates local on
a451ba0, rustc 1.96.0: fmt clean, clippy clean, 287 passed / 0 failed.