Enable automatic scheduled releases - #128
Merged
Merged
Conversation
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.
🚀 Pull Request
Summary
Enable settled scheduled candidates to publish automatically after every release gate passes.
Related Issues
None.
Changes
Description
Scheduled runs now satisfy the publication trigger without workflow-dispatch inputs. They still require successful detection, validation, packaging, SQL Server restore-forward verification, the F1SQL_RELEASE_BUNDLE_READY repository variable, and the protected production environment. Manual runs retain both explicit dry-run and publish safeguards.
Screenshots
Not applicable.
Testing
Local verification: 73 tests passed; mypy and Ruff passed; release workflow YAML parsed successfully.