bowenliang123 opened a new issue, #7597:
URL: https://github.com/apache/kyuubi/issues/7597

   ## Description
   
   `actions/labeler@v7` fails to parse `.github/labeler.yml` and aborts the 
workflow before applying any labels:
   
   ```
   Run actions/labeler@v7
   The configuration file (path: .github/labeler.yml) was not found locally, 
fetching via the api
   Error: YAMLException: deficient indentation (24:7)
   
    21 | "kind:build":
    22 |   - changed-files:
    23 |     - any-glob-to-any-file: [
    24 |       '.dockerignore',
   ------------^
    25 |       '.rat-excludes',
    26 |       '.scalafmt',
   ```
   
   ## Root cause
   
   The file uses YAML flow-style sequences (`[ ... ]`) split across multiple 
lines, with the continuation lines indented at 6 spaces while the opening 
bracket is at column 27. YAML 1.2 (and `js-yaml@4`, which `actions/labeler@v7` 
depends on) requires flow-sequence continuations to be indented at least one 
column past the opening bracket, so every block in this file fails with the 
same error.
   
   The format was introduced in commit `7e96dc7bc9` (Dec 19, 2023, #5874) when 
the action was bumped from v4 to v5. v5/v6 bundled an older `js-yaml` that did 
not strictly enforce the indentation rule, so the bug was latent until #7583 
bumped the action to v7.
   
   ## Proposal
   
   Rewrite all `any-glob-to-any-file: [ ... ]` / `all-globs-to-any-file: [ ... 
]` blocks in `.github/labeler.yml` as standard block-style sequences so the 
file parses under strict YAML 1.2 and remains compatible with 
`actions/labeler@v7` (and future versions).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to