fix(ci): valid Windows workflow YAML (colon broke parse) + probe results - #113
Merged
Conversation
The Build step name had a colon-space ('cross-platform: rimraf …') which made
GitHub reject the whole workflow ('workflow file issue') and never register
workflow_dispatch. Removed the colon so the probe actually runs.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
✅ Docker image built successfully
|
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.
The Windows probe (#43) workflow had a colon-space in a step name (
Build (cross-platform: rimraf …)) → GitHub rejected the whole file ("workflow file issue") and never registeredworkflow_dispatch. Removed the colon; YAML now valid (verified locally with a yaml parser).First real Windows probe result (windows-latest): Install ✓, Build ✓ — the cross-platform build (#1.28.2) is confirmed working on native Windows. Unit tests ✗ (fails fast at startup; the specific failures aren't capturable from gh's truncated logs — needs Windows-side diagnosis). That's the next #43 layer (runtime blockers: POSIX hooks / tar / ACLs / path handling surfaced via the test suite).
🤖 Generated with Claude Code