Repository navigation
chore: validate workflows before CI checks - #809
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
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.
Summary
Validate every workflow with pinned actionlint and ShellCheck before starting application checks, and include that result in the required CI Gate. Bound frontend/backend checks and the Windows release build with explicit job timeouts so stalled runs cannot consume the default six-hour allowance.
Related Issue
Not applicable.
Verification
actionlint 1.7.12with ShellCheck 0.11.0 passed on all workflow files.pnpm exec oxfmt --check .github/workflows/ci.yml .github/workflows/release.yml CONTRIBUTING.mdpassed.Not verified: no release tag was created to exercise the release timeout.
Notes
The 45-minute release budget leaves headroom over recent successful releases, which completed in roughly 20–22 minutes.