Pin the Unraid template to 0.15.1 - #456
Merged
Merged
Conversation
Moves Community Applications off edge and back onto a specific published tag. edge is rebuilt on every merge to main, so Unraid users were running whatever landed most recently, before it was tagged or verified. Desktop users are only offered a build once a release has been promoted by hand, specifically so nothing reaches them inside the verification window. Unraid had no such window. It also made bug reports hard to act on: edge from Tuesday and edge from Thursday are different software with the same name. 0.15.1 rather than 0.15.0 because 0.15.0's macOS build failed on the QuickJS arch mapping (#454) and 0.15.1 is the first tag carrying that fix. The image publishes on release: published, so this pin only becomes valid once 0.15.1 is published, and the template on main is what Community Applications serves live. Landing it earlier would give every Unraid user a pull failure.
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.
Closes #453
Moves Community Applications off
edgeand onto a specific published tag.edgeis rebuilt on every merge tomain, so Unraid users have been running whatever landed most recently, before it was tagged or verified. Desktop users are only offered a build once a release has been promoted by hand, precisely so nothing reaches them inside the verification window. Unraid had no such window at all.It also made bug reports hard to act on:
edgefrom Tuesday andedgefrom Thursday are different software with the same name.Why 0.15.1 and not 0.15.0
0.15.0's macOS build failed on the QuickJS arch mapping (#454). 0.15.1 is the first tag carrying that fix, so it is the first one worth pinning.
Do not merge before 0.15.1 is published
The image publishes on the
release: publishedevent, and the template onmainis what Community Applications serves live. Merging this before 0.15.1 exists gives every Unraid user a pull failure.Sequence: publish 0.15.1, confirm
ghcr.io/stemdeckapp/stemdeck:0.15.1exists, then merge this.