Repository navigation
chore: Schedule maintenance checks and keep release references precise - #636
Merged
Merged
Conversation
Contributor
|
Thanks for your contribution! Code follows dev → beta → main. Standalone docs/blueprints follow content → main. Please change this PR's base branch using Edit next to the title. You do not need to close and recreate the PR. See CONTRIBUTING.md. |
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.
Run weekly compatibility, performance, source-review and dependency checks against dev while stable branches retain their agreed transitional test baseline. Add a regression fix so Markdown links to other repositories or PRs never notify unrelated local issues.
The schedule uses the existing trusted workflow entry point on main and checks out dev explicitly; it does not move integration code into stable. Full PR/release gates on main/content still activate with normal code promotion. Verified with actionlint and offline issue-reference tests.