chore: pin Unraid template to 0.12.0 - #395
Closed
thcp wants to merge 1 commit into
Closed
Conversation
The template pins an exact published image tag, so this must not land before ghcr.io/stemdeckapp/stemdeck:0.12.0 exists. Kept separate from the code-signing PR for that reason.
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.
Bumps
templates/stemdeck.xmlfrom0.11.1to0.12.0.Do not merge before the image exists
Unraid pulls this exact tag.
ghcr.io/stemdeckapp/stemdeck:0.12.0is only pushed bydocker-publish.ymlwhen the 0.12.0 release is published, so merging this first leavesmainpointing at a tag that 404s for anyone installing in the gap.Merge order: publish release 0.12.0 -> wait for
docker-publish.ymlto push the image -> merge this.Split out of #394 for that reason; #394 has no such ordering constraint.