Proposals that say what they compared
Pull request checks now name the branch and snapshot they were diffed against, drop out of the list when their changes land, and survive a flaky upstream.
In this release
- New
Every proposal names its baseline
A change count only means something next to what it was measured against, so proposals spell out the branch and snapshot they were diffed with.
- Improved
Pull requests leave the list when their changes do
A PR whose changes were merged or reverted drops out of the proposals list instead of lingering with a stale count.
- Fixed
CI rides out GitHub and Cloudflare blips
Transient upstream failures are retried and logged with what actually went wrong, rather than failing your build or posting a misleading comment.
"14 changes" is not information. Fourteen changes against what is.
Proposals — the schema diff we post on a pull request — now state their baseline: the branch they compared against, the snapshot version of it, and when that snapshot was taken. When a PR branched from a base that has since moved, the comment says which base it used rather than silently comparing against whatever was newest.
A list that keeps up
A proposal used to linger after its changes were merged or reverted, sitting in the list with a count that no longer described anything. Proposals now leave the list when their changes stop being changes.
Failing loudly, in the right place
Two kinds of noise were coming out of CI: transient GitHub and Cloudflare errors that failed an otherwise fine build, and a stale-branch warning attached to comments where nothing had changed at all. Upstream blips are now retried, and what actually failed is logged instead of a generic wrapper. Your build fails when your schema has a problem — not when a network did.