Repository navigation
π docs(fork): record what the fleet actually runs - #164
Merged
Merged
Conversation
Signed-off-by: James Reilly <jreilly1821@gmail.com>
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.
FORK.md said the fleet tracks
v4. Since 2026-10-29 hub, school and reef run a fork build (tuna/fleet@ 911e5c0, upstream v5 + three patches) bind-mounted over the v6 image on the Spindle VPS. Records the build, its delta and where each patch stands upstream (hivecommons#15049, hivecommons#15329), and how to verify the running binary. Default branch staysv4because the hourlyhive-healthworkflow lives here. Tracker: tuna-os/tunaOS#4072.