Gate
gstack 1.91.192.0: merge trains stop passing a damaged CHANGELOG
gstack's merge train version gate read the changelog through a one megabyte buffer. Past that, it compared two empty strings and passed. Now it reads up to 64 megabytes, and refuses a changelog it can't open.
Conflict
A PR that drops a released heading now stops the train merge
When a PR's changelog dropped or renamed a released heading, the train merge carried that damage into the train. Now that PR stops as a changelog conflict with the reason, for you to resolve by hand.
Order
You can now set the order a train slots its PRs
Trains slot PRs by screening, then by ready order, which once put a docs PR ahead of the change it describes. Now you can name the order yourself, and later rebuilds keep it.
Fixes
Receipts, verify and restamp also stop tripping trains
Ready receipts are now found whatever URL your lane's origin uses. A correct hand-resolved head passes train verify, as long as it contains main. And restamp reads large changelogs too.
Next
If you run merge trains on a big CHANGELOG, I would upgrade before the next train
CHANGELOG.mdgarrytan/gstack · 1.91.192.0If you run merge trains on a changelog past a megabyte, I would upgrade gstack before the next train, because that is where damage slipped through. The details are in the changelog.
