Add standalone CLI lifecycle and release packaging - #92
Merged
Conversation
Contributor
Author
|
Additional tooling context: I added |
rugbedbugg
force-pushed
the
feature/standalone-cli
branch
2 times, most recently
from
September 2, 2026 07:00
10d00a5 to
e7ffbc2
Compare
lavan8t
previously approved these changes
Sep 2, 2026
lavan8t
left a comment
Member
There was a problem hiding this comment.
running latch-cli --status says latched: no even while the desktop app is open and latched.
rugbedbugg
force-pushed
the
feature/standalone-cli
branch
from
September 2, 2026 17:36
e7ffbc2 to
87e89c3
Compare
This was referenced Sep 3, 2026
rugbedbugg
added a commit
that referenced
this pull request
Sep 3, 2026
android.yml is the only PR-triggered workflow and runs assembleDebug, testDebugUnitTest and :app:lintDebug, all of which stop at :core's androidTarget. :desktop and :cli have never been compiled on a PR, and :core's desktopTest source set has never been run. The gap is not theoretical. PR #113 bumps composeMaterial3Mp, which is consumed only by :desktop, and passed CI without that module being built. PR #92 adds 13 test files under core/src/desktopTest and cli/src/test that no current job would execute. Runs on ubuntu-latest only: :desktop is a single jvm("desktop") target, so one host covers the Kotlin/Compose surface, and per-OS packaging is already exercised by release.yml.
rugbedbugg
added a commit
that referenced
this pull request
Sep 3, 2026
* [CI]: Add Desktop CI for :desktop, :core desktopTest and :cli android.yml is the only PR-triggered workflow and runs assembleDebug, testDebugUnitTest and :app:lintDebug, all of which stop at :core's androidTarget. :desktop and :cli have never been compiled on a PR, and :core's desktopTest source set has never been run. The gap is not theoretical. PR #113 bumps composeMaterial3Mp, which is consumed only by :desktop, and passed CI without that module being built. PR #92 adds 13 test files under core/src/desktopTest and cli/src/test that no current job would execute. Runs on ubuntu-latest only: :desktop is a single jvm("desktop") target, so one host covers the Kotlin/Compose surface, and per-OS packaging is already exercised by release.yml. * [CI]: Rename Desktop CI job to avoid check-name collision Both workflows declared a job id of `build`, so the PR checks list showed two entries named `build` with no way to tell the Android job from the desktop one. Renaming this job to `desktop` makes the check read "Desktop CI / desktop", which also matters if it is ever promoted to a required status check.
rugbedbugg
force-pushed
the
feature/standalone-cli
branch
from
September 3, 2026 05:58
87e89c3 to
8b8f48f
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.
Summary
latch-cliapplication for Linux terminals and Windows PowerShell.latch-cliand Latch Desktop through one authenticated local runtime owner.latch-cliand persist the background daemon withactivateanddeactivate..deband.rpmartifacts.latch-cli-binAUR andVinnovateIT.LatchCLIwinget metadata.Verification
mise exec -- ./gradlew check :cli:packageCliAppImage --rerun-tasks --console=plain.activate,--status, and repeateddeactivate.