fix(ci): point the preset validator at the renamed file - #6
Merged
Conversation
The rename PR (#4) moved default.json5 → default.json but missed the CI workflow, which is hardcoded to the old filename. Every run since has failed with `File does not exist "default.json5"` — PR #4 and PR #5 both merged past a red check because the check isn't required. Point the validator at default.json. Confirmed locally: exit 0, "Config validated successfully" (with the harmless JSON5-in-.json deprecation warn, which does not fail --strict).
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 rename PR (#4) moved
default.json5→default.jsonbut missed this workflow, which is hardcoded to the old filename. Every run since has failed withFile does not exist "default.json5"— PR #4 and PR #5 both merged past a red check because the check isn't required.Point the validator at
default.json. Confirmed locally: exit 0,Config validated successfully(with the harmless JSON5-in-.json deprecation warn, which does not fail--strict).