This repository was archived by the owner on Oct 30, 2026. It is now read-only.
Repository navigation
Prepare CLI v0.1.10 with J71b-compatible hardware - #1
Merged
Merged
Conversation
This was referenced Oct 27, 2026
Contributor
Author
|
Synchronized release set: hardware v0.1.10 → CLI v0.1.10 → BOTH OrchardLinux/minimal-linux#1 and OrchardLinux/omarchy-a#3 (v0.1.1) → shared launcher OrchardLinux/orchard#4 containing both new roots. No Omarchy-only shortcut. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Scope
Refs OrchardLinux/orchard#1 and OrchardLinux/orchard#3.
Validation
136 CLI tests pass locally against hardware 0.1.10; diff check passes.
Dependency gate
Do not merge/tag until hardware v0.1.10 is publicly available. CI reads that exact release, not a sibling checkout or local artifacts.
After passing CI: merge, tag v0.1.10, and publish the CI-produced draft. No local image build or device action is required.