Repository navigation
Package Callimachus for Snap Store using signed-release assets - #22
Merged
Merged
Conversation
CLA verifiedAll identified contributors are covered by the Callimachus CLA check. ✅ |
SNatangelo
marked this pull request as ready for review
November 4, 2026 14:12
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.
What this adds
core22Snap recipe for the existing Linux amd64 desktop bundle, pinned to the release asset's SHA-256.prepare_snap_release.pyresolves each published GitHub release's Linux archive and checksum..snapfor testing, and uploads to the Snap Storeedgechannel when the publisher secret is present.Validation
callimachus-snapartifact created.snapcraftproduced a package (~352 MB).stable.password-manager-serviceandremovable-mediaare not automatically connected; test Guided Fetch, settings, keyring, and file access in confinement.edgemay still require manual review.The existing release pipeline is unchanged; no automatic stable publication.