snap: use snapcore/action-build for candidate builds #1566
Merged
Conversation
This file contains 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.
This switches the snap candidate builds to use the official
snapcore/action-buildGitHub Action rather than our bespoke Docker build.Additionally it updates the snap base tocore22,This built successfully in my fork (note it is red as the upload failed due to the missing credentials, but the build itself succeeded):
https://github.com/andrewsomething/doctl/actions/runs/10359056705/job/28674610325#step:3:98
Once we've successfully built, uploaded, and validated a new candidate snap, I'll follow on with a new PR for the release workflow. Then finally, after successfully cutting a new release, we can rip out the Docker build scripts.