feat: publish signed desktop CLI artifacts - #17
Merged
ImPedro29 merged 3 commits intoAug 8, 2026
Merged
Conversation
graseeel
marked this pull request as ready for review
August 8, 2026 21:17
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
Security and ownership
Pull request jobs only upload short-lived Actions artifacts. They contain no GitHub Release upload path and receive no production signing key. The production job runs only in verbeux-ai/code, fails closed without the protected secrets, verifies the signature before trusting manifest JSON, and never overwrites an existing release asset.
The packaging gate also inspects the built
dist/cli.mjsartifact and refuses publication if the TodoWrite contract consumed by Verboo Desktop disappears or is reduced to an orphan marker.Maintainer setup required
This PR intentionally cannot publish production desktop assets until the protected release environment contains:
The setup, release, rotation, and compromise procedures are documented in docs/desktop-cli-distribution.md.
Verification
The repository-wide TypeScript baseline and two existing release-critical imports already fail on upstream main because mirrored modules/assets are absent; this PR does not modify or mask those unrelated failures.