Repository navigation
Publish successful scheduled DD-Turnip builds as the latest release - #15
Merged
Merged
Conversation
maxjivi05
force-pushed
the
ci/publish-scheduled-builds
branch
from
November 8, 2026 15:08
cf2a0c5 to
7866898
Compare
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.
Scheduled
release.ymlruns used to publish a prerelease that waited forpromote.yml. A successful scheduled run now publishes straight to Drivers-CI and is marked latest, like a manual run. ThePrereleasecheckbox on manual runs still keeps a build off Drivers-CI until it is promoted.release.yml:PRERELEASEis only true for a manual run withPrereleaseticked.README.md: workflow section updated to match.A failed build still publishes nothing (the release job needs both builds), and the follow-Mesa issue behaviour is unchanged.