CI: build snap without snapcore/action-build#4527
Merged
Merged
Conversation
The action is effectively unmaintained (snapcore/action-build#1 has been open since April with no maintainer response). Replace it with a direct snapcraft invocation using --destructive-mode, which builds on the runner host instead of in LXD. Pin the job to ubuntu-24.04 so the host matches the snap's core24 base.
This step set a snap_channel output that's not consumed anywhere; the last consumer was removed in d3530f4 when snap releases stopped happening from GitHub Actions.
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
snapcore/action-build appears effectively unmaintained: snapcore/action-build#1 (updating the action's Node.js runtime to node24) has been open since April with no maintainer response. As GitHub's node20 deprecation rolls in, this action becomes a liability.
Replace it with two inline steps:
sudo snap install --classic snapcraftsudo snapcraft --destructive-mode, with the sameSNAPCRAFT_BUILD_INFOandSNAPCRAFT_IMAGE_INFOenv vars the action used to set.--destructive-modebuilds directly on the runner (no LXD), which is faster and simpler. The job is pinned toubuntu-24.04so the host always matches the snap'sbase: core24.Test plan
Linux (snap)job and producestiled_*_amd64.snapsnap/manifest.yaml(fromSNAPCRAFT_BUILD_INFO=1)