refactor(fleet): dispatch suites with rc inputs and drop parent repin and floor gate - #470
Merged
Merged
Conversation
… and floor gate Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
joshua-temple
force-pushed
the
feat/fleet-dispatch-selfrepin-flip
branch
from
July 5, 2026 20:09
32ecb86 to
57e5e4f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The fleet pinned every example repo to the candidate from a central parent
repinjob before fan-out, and afloor-checkjob (plus the daily suite-tooling-floor workflow and its script) guarded suite bootstrap pins. With the suites now able to self-repin from a dispatched version, that central machinery is redundant: it duplicates work each suite can do on its own main, and the floor gate is superseded by the release-triggered bootstrap-pin bump.Change
resolvenow also peels the resolved rc tag to its commit sha and exposes it as a second outputcascade_version_sha(guarded so an empty version stays a clean no-op).resolveinstead of the parent repin, and forwardscascade_version+cascade_version_shato itsdispatch-suitestep so the suite self-repins to the version under test.repinjob, thefloor-checkjob,.github/scripts/check-suite-tooling-floor.sh, and.github/workflows/suite-tooling-floor.yaml.aggregatedrops thefloor-check/repinneeds, env vars, and table rows while preserving the resolve check, the candidate-version check, the per-lane success-or-skipped rule, and the fail-closed no-lane-ran guard.dispatch-suiteNOTE corrected to say the version is forwarded only when non-empty.Verification
actionlintclean on the fleet and bootstrap-pin workflows.repin-job /floor-check/suite-tooling-floorreferences remain (only the new self-repin vocabulary).go build ./...,go test ./...(2364 passing), andgolangci-lint run ./...all clean.