Repository navigation
Fix rejected CI/release workflows and validate Actions expressions - #7
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.
After the workflow optimization, both cross-platform CI and release were rejected before any jobs started. PACE_CONTROLLER_DATA_DIR referenced runner.temp inside jobs..env, where GitHub does not allow the runner context. This blocked releases after merges of both #6 and #5; #5's original PR tests passed.
Move the temporary data directory to the test/render steps, where runner.temp is valid, and retain the shared offscreen settings at job level. Add pinned actionlint validation to the existing source CI job, with pip caching, to reject invalid workflow expressions before merging.
Validation: actionlint 1.7.12 reproduces the original runner-context error and passes all six corrected workflows. 34 cross-platform tests and 7 repository checks pass locally. GitHub CI and release still require remote execution; this PR corrects the shared cause rather than rerunning the invalid definitions.