Repository navigation
Simplify Actions validation and clarify workflow targets - #12
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.
Run the recipe's complete checks once through its known validation route, followed by one required
Build & Testresult. Remove duplicate Fast validation and runtime routing from the generated caller. Keep native platform/shard coverage, artifact/source checks, declared runners and original deadlines.Regenerate with qualified Cookbook source
f1c6a5d224776bcee5128a8ce91392483af22566(Cookbook PR40 and UTF-8 admission fix PR41). Give merge, CI, preview and release runs clear target names, and update dependency policy to wait for the new result.Validation: canonical generation and
--checkpass; actionlint passes. Full configured Actions checks run on this PR and separately on Main after merge. Existing required-check contexts are migrated after the replacement checks pass.Generated UTF-8 workflow text now passes canonical admission on Windows independently of its locale; altered workflow content remains a refusal.