Development record
The merge hold that abcd land respects (claim.Hold, read by releaseHolds) still reads a release as ended as soon as any tombstone sits on its reservation branch, whoever pushed it. The release hold now ends a release only on a tombstone its holder pushed or on its tag, for the second-release refusal, the launch reading and peers, so the two readings of one release can disagree: land lets merges through while the launch check still names the release as being cut. The land hold already ends when its lease lapses, so it is a time-boxed courtesy and the withdrawal is the hold that keeps merges out; the disagreement is in what each surface reports.
The merge hold that abcd land respects (claim.Hold, read by releaseHolds) still reads a release as ended as soon as any tombstone sits on its reservation branch, whoever pushed it. The release hold now ends a release only on a tombstone its holder pushed or on its tag, for the second-release refusal, the launch reading and peers, so the two readings of one release can disagree: land lets merges through while the launch check still names the release as being cut. The land hold already ends when its lease lapses, so it is a time-boxed courtesy and the withdrawal is the hold that keeps merges out; the disagreement is in what each surface reports.
Frontmatter
| id | iss-2610230927379322 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610230927379322-the-merge-hold-that-abcd-land-respects.md
open on GitHub ↗ · commit history ↗
mentions1
- dcn-26102309282719392026-10-23 — The finding in iss-2610230927379322 is deferred out of the release-hold change (iss-2610222014550692), ruled by the coordinating facilitator on delegation while the product thinker is away: the merge hold that abcd land respects still reads any tombstone on a release reservation as the release's end, whoever pushed it, so land and the launch check can disagree about one release. Reason: the land hold already ends when its lease lapses, so it is a time-boxed courtesy; the withdrawal the release-hold change adds is what keeps merges out; and a change to every land check deserves its own review. The same session fixes it as its first work once the release-hold pull request lands, not at a later date.