Repository navigation
Publish apps through GitHub releases and Hub issues without developer keys - #167
Merged
Merged
Conversation
ymote
marked this pull request as ready for review
October 8, 2026 06:56
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.
Opening an App Hub issue requests publication, for first versions and updates. The previous default instructions asked developers to generate and retain an Ed25519 publisher key. This change installs a GitHub tag-release workflow that attests the exact app manifest and bundle digest using GitHub's job identity, without a developer signing key or repository signing secret. The resulting release pack is review evidence for the issue; a Hub administrator still reviews and approves admission.
tools/octo newincludes the workflow;publish-githubadds it to existing editable repositories without overwriting custom automation. Tools preserve sealed releases: check does not restamp them, and run refuses them before startup or file writes. English/Chinese guides distinguish the default publishing path from optional legacy local-store rehearsals. The template's Add button also retains its visible colors when focused, a defect found in the real fixture run.Validation:
App Hub #153 and #154 are merged. The generated workflow pins merged toolchain
655114c4943cd2490daaefa2173e7b5aaa20669f; app-contract 1.8.0 is published on crates.io (publication run 37739082884). The two original fixture workflows used public sourcec11de1d7, as recorded in their receipts. A compatible OctoSense release and shell/phone installation acceptance remain pending. No fixture submission issue was opened and no fixture was added to the public catalog.