Repository navigation
fix: resolve #12355 - dev-fleet: differentiate the unresolved-channel notice on an - #12356
Conversation
Dev Fleet manages git checkouts, and a git checkout has no release channel —
`platform/update_capability.py` says so outright: "Only the wheel command
carries a channel. A git checkout follows its remote." That leaves no way to
run what stable actually shipped next to unreleased work.
Adds ONE detached worktree pinned to the stable channel, named
`release-channel-stable` as a sibling of the primary checkout, appearing as an
ordinary fleet row that pods and Make Live already drive.
Why not a pin on the primary checkout: sync fast-forwards it (`merge --ff-only`)
and refuses unless HEAD is literally `BASE_BRANCH`. A stable tag is normally
BEHIND main, so pinning that checkout could only work by detaching its HEAD —
which the sync guard rejects, and which repoints every origin/main comparison on
the row — or by resetting main backwards, which destroys work.
Not coupled to the update channel: nothing reads or writes
`$KIROCREW_HOME/channel`. That file says which lane the user's install FOLLOWS
for updates; a pin here says which ref a worktree SITS ON. There is one channel
and it is a single `CHANNEL = "stable"` constant, not a lane vocabulary — an
unpublished lane is a state of that channel, never a second kind of row.
Resolution takes the newest `vX.Y.Z` in SEMVER-DESCENDING order. Tag creation
date is not the ordering: a retagged or backfilled release publishes out of
order, and "newest release" is a claim about version precedence rather than
about when someone pushed the tag.
Resolution is sourced from a private pruned tag mirror
(`refs/dev-fleet/release-tags/`), fetched under a checked refspec, so a local tag
cannot decide what gets checked out — a forged `v9.9.9` in the operator's own
clone resolves nothing. An `ls-remote` provenance check closes the window
between resolving a tag and checking it out, and `repo_supplied_filter` refuses
repo-configured content filters so a fetched repository cannot run its own code
during the checkout; both run inside `_GIT_MUTATION_LOCK`.
`release-channel-*` is reserved, so adoption requires the SHAPE (detached),
never the name — a user's branch checkout under that name keeps ordinary
controls and its ordinary behind-main count, and reports that it is not a
release worktree rather than being silently adopted.
Create only: there is no in-place mutation of a pin. A pinned tree that moved on
its own would shift under a pod being debugged, and an explicit Advance turned
out to be the mechanism forcing every unpleasant tradeoff around it, so moving a
pin is Remove followed by Create — two visible acts on the row that owns them.
Fleet payload gains `release_channel`, its own key rather than extra `worktrees`
rows: a channel with no worktree has no path, and every consumer of a worktrees
entry assumes one. On this row BEHIND measures distance from the CHANNEL TIP (the
behind-main figure is large by construction and names no action) and PR renders
as inapplicable rather than as the no-PR dash. Because the Behind column header
is one shared element above rows with two different denominators, it names both.
Adds `website/capture/devfleet-release-channel.{tsx,html}` and
`website/scripts/capture-devfleet-release-channel.mjs`, the committed harness
that renders the three row states — adopted, placeholder, reserved-name branch —
against the real page with `fetch` stubbed at the network seam.
…ed-channel notice on an
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
…ed-channel notice on an
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
6 similar comments
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
Consolidation: this branch carries an older snapshot of PR #10066; port its last head before this lands PR #10066 was closed today in favour of this PR. The first commit here,
Only this PR has the Suggested path:
The security-fenced Create TOCTOU finding from #10066's review (deferred to issue #12342) applies unchanged to the same code here. This PR covers only part of issue #12355, so "Closes #12355" overstates what it does. From a full open-PR audit against origin/main c66f95b (2026-09-25); findings were checked by independent reviewers reading the code. Reply here if this is wrong. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
5 similar comments
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
15 similar comments
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
Rebase needed: this branch now conflicts with main in 7 files This branch has not changed since 2026-09-21 (head What I checked on the current head:
Suggested next steps: port #10066's last head as described above, then rebase onto current main and resolve the 7 conflicts. Also note that issue #12355 is only partly addressed here. From an open-PR triage against origin/main a92dde1 (2026-10-05). |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
5 similar comments
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
👋 Hi! This PR's description is missing some required sections from our PR template. Workflow runs won't be auto-approved until the description is updated. Missing sections:
Please update your PR description to include these sections, then push or re-save the description. The workflows will be approved on the next cycle. |
|
@fathirramadhan-web thanks for this PR. It has merge conflicts with If there is no activity here or on #12355 by 2026-10-22 (14 days), we will close both as stale. You are welcome to reopen after that. |
|
Thank you for picking this up, @fathirramadhan-web. Issue #12355 was closed as not planned on 2026-10-17 because the release-channel rows this notice belongs to came from #10066, which was closed without merging. |
Closes #12355
Overview
Addresses the problem reported in #12355 by resolving the underlying issue and ensuring test coverage passes.
Verification