Conversation
The v6.18.40 build never started: my previous commit added a second env: block to the release step rather than merging into the existing one, and GitHub rejects that with "'env' is already defined" before running any job. Merged them. The reason it got pushed is the check I was relying on: yaml.safe_load accepts duplicate mapping keys and keeps the last one, so the file parsed cleanly here and was rejected there. scripts/lint-workflows.py now loads with a constructor that refuses duplicates, and reports the same location GitHub does - "duplicate key 'env' at line 170, column 9" against "(Line: 170, Col: 9): 'env' is already defined" - plus it fails a workflow with no jobs. Verified against a deliberately broken copy. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 v6.18.40 build never started: my previous commit added a second env: block to the release step rather than merging into the existing one, and GitHub rejects that with "'env' is already defined" before running any job. Merged them.
The reason it got pushed is the check I was relying on: yaml.safe_load accepts duplicate mapping keys and keeps the last one, so the file parsed cleanly here and was rejected there. scripts/lint-workflows.py now loads with a constructor that refuses duplicates, and reports the same location GitHub does - "duplicate key 'env' at line 170, column 9" against "(Line: 170, Col: 9): 'env' is already defined" - plus it fails a workflow with no jobs. Verified against a deliberately broken copy.