sean/builder-images
Watch
1
0
Fork
You've already forked builder-images
 0
Code Issues Pull requests Projects Releases 144 Packages Wiki Activity

fix(dockerfile-set): publish the pull-request fetch fix as v7 #245

Merged
binjovi-bot merged 1 commit from sean/publish-buildkit-client-v7 into trunk 2026-09-09 08:20:34 +00:00 AGit
Conversation 0 Commits 1 Files changed 2 +7 -1
sean commented 2026-09-09 08:19:56 +00:00
Owner
Copy link

VERSION 6 carries the fix that lets binjovi-dockerfile-set build a pull request at all, but it was never published -- the release that would have failed in promoting on an unrelated bug (the item publish inherited a 60-minute BUILD budget, over the agent's 30-minute bound). That is fixed now, but the 5->6 change is already in the release's own base so no later diff can rediscover it and resume cannot recreate the promotion. The same fix ships as v7. A second bump is the honest cost of a release lost between two bugs, and cheaper than leaving the fleet on a tool that cannot build a pull request. https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76

VERSION 6 carries the fix that lets binjovi-dockerfile-set build a pull request at all, but it was never published -- the release that would have failed in promoting on an unrelated bug (the item publish inherited a 60-minute BUILD budget, over the agent's 30-minute bound). That is fixed now, but the 5->6 change is already in the release's own base so no later diff can rediscover it and resume cannot recreate the promotion. The same fix ships as v7. A second bump is the honest cost of a release lost between two bugs, and cheaper than leaving the fleet on a tool that cannot build a pull request. https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76
fix(dockerfile-set): publish the pull-request fetch fix as v7
All checks were successful
binjovi/ci Binjovi completed the frozen plan
Details
7fe4851ad0
 
VERSION 6 carries the fix that lets `binjovi-dockerfile-set` build a pull
request at all -- a plain `git clone` fetches no `refs/pull`, so before it the
tool failed with "source revision is absent" on every PR it was given. It was
built and it is sitting in quarantine, but it was never published, so the
agents still run v5.

The release that would have published it failed in `promoting`, on an
unrelated bug: the item publish inherited this project's 60-minute BUILD budget
and the agent refuses an `oci_publish_item.v1` task above 30 minutes. That is
fixed now (binjovi v0.1.517), but by then the VERSION 5 -> 6 change was already
in the release's own base revision, so no later diff could rediscover it and
`resume` could not recreate the promotion.

So the same fix ships as VERSION 7. Nothing in the script changes except the
note recording why the number moved; a second bump is the honest cost of a
release that was lost between two bugs, and it is cheaper than leaving the
fleet on a tool that cannot build a pull request.

Claude-Session: https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sean/builder-images!245
No description provided.