chore: gate stable and add promotion action #1742
Merged
+63
−1
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.
The autoupdater pushed a partial update today, and the previous update broke the framework kmod (because it is now "upstream")
The update regression rate is too high for the current state of bazzite, for the vast majority of its users.
That being said, there are a lot of users that like to be a bit ahead.
Therefore, gate the stable builds behind an
edge
tag for power users, and add a small action to promote the currentedge
build tostable
once it has been validated to work.Just in time for F41.
The regression in this update was small: the Ally frame limiter stopped working and we were caught by surprise. It would have been worse, as with F41. The edge channel also allows us to update that channel to F41 earlier than Fedora.