ci: add manual snap store metadata push workflow#26
Merged
Conversation
One-shot resync for cases where the snap store description has drifted from snap/snapcraft.yaml (e.g. when a release predates the auto-push step added in PR #25). Trigger via 'gh workflow run snap-push-metadata.yml'. The release.yml publish-snap job handles this automatically from v0.1.12 onward; this workflow exists for manual one-offs.
aydiler
added a commit
that referenced
this pull request
May 24, 2026
…#27) snapcraft 8.x removed the --from-yaml flag. Metadata is now read from the .snap file's embedded yaml. Both push-metadata sites (the one-shot manual workflow and the publish-snap step in release.yml) need to: 1. Build a fresh snap first (so the new snap/snapcraft.yaml is embedded) 2. Call snapcraft push-metadata <snap-file> --force (no --from-yaml) For the manual workflow this means swapping the 'snap download' step for snapcore/action-build@v1 — slower (~15 min LXD build) but correct. For release.yml the build is already happening for the publish step, so only the flag change is needed. Reproducer: the snap-push-metadata workflow run dispatched after PR #26 failed with 'Error: No such option: --from-yaml'.
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
1 participant
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
One-shot manually-triggered workflow that pushes snap/snapcraft.yaml's description and summary to the Snap Store listing.
The release.yml publish-snap job already does this automatically from v0.1.12 onward (added in PR #25). This workflow exists for the gap where v0.1.11 shipped before the auto-push was wired in — the store listing description still shows the pre-v0.1.4 short version.
After this merges, I'll trigger it once with `gh workflow run snap-push-metadata.yml`.
Test plan