Restamp
gstack’s /ship stamps a PR’s version when it is next to merge
gstack-restamp --nextone stepReordering a release queue meant hand-editing the version, changelog headings and lockfile on every pull request behind it. Now gstack-restamp stamps a pull request when it is next to merge, and /ship runs it for you.
Policy
A committed ship policy sets how each repo bumps and stamps
Each repo now commits a ship policy: its bump rule, queue mode and the files that carry the stamp. gstack reads it from the base branch, and when the rule is bump patch, ship stops asking for a version.
Gate reuse
The gate can be reused when the stamp is the only change
TREE: same-modulo-stampsgate-reuse: eligibleTREE: changed (<paths>)not-eligible + fixA new stamp meant a full gate run on a tree that differed by a few bytes. Now a tree receipt proves the stamp is the only change, so the earlier gate counts. Stamp-sensitive lanes still rerun.
Receipt
Every PR body now opens with a ship receipt
gstack-evidence bundle · gate results a fresh machine can check/ship now writes a receipt as the first block of the pull request, with the tree verdict, gate reuse and policy. An evidence bundle carries the gate results to a fresh machine after the gate's VM is gone.
Limits
Mirroring waits for a later release
mirror is validated, then skippedPOLICY_SOURCE_UNAVAILABLEdocs/ship-policy.mdsetting up a policyThe policy's mirror setting is checked but skipped for now. A shallow checkout can't read the policy from the base branch. And gstack's own repo still claims a version when a pull request opens. The ship policy guide covers setup.
