uros-b opened a new pull request, #17382:
URL: https://github.com/apache/iceberg/pull/17382
## What / Why
The `triage` job (`.github/workflows/labeler.yml`) is currently **failing on
every PR** with:
```
##[error]YAMLException: deficient indentation (24:7)
23 | - any-glob-to-any-file: [
24 | '.asf.yaml',
------------^
```
### Root cause
#17371 bumped `actions/labeler` from **v6.2.0 → v7.0.0**. That release
upgraded the action's bundled `js-yaml` dependency from `^4.2.0` to `^5.1.0`.
The js-yaml **5.0.0** major release expanded YAML 1.2 conformance and tightened
block/flow parsing.
Under the stricter parser, the multi-line **flow sequences** (`[ ... ]`) in
`labeler.yml` are now rejected: the list entries were indented to the *same*
column as their parent `any-glob-to-any-file:` key rather than deeper, which
the new parser flags as "deficient indentation". The action reads this config
from the base branch, so the error appears on all PRs regardless of their
contents. `labeler.yml` itself has not changed since May 2025 — the parser
under it got stricter.
### Fix
Convert the multi-line flow sequences to **block sequences**, which parse
cleanly under the new parser and are the idiomatic labeler syntax. This is a
**pure syntax change** — the parsed configuration is equivalent (same labels,
same globs), verified by parsing both the old and new file and confirming the
loaded structures are deep-equal. Also drops a stray trailing comma in the
`HIVE` block.
Before:
```yaml
INFRA:
- changed-files:
- any-glob-to-any-file: [
'.asf.yaml',
'.gitattributes',
]
```
After:
```yaml
INFRA:
- changed-files:
- any-glob-to-any-file:
- '.asf.yaml'
- '.gitattributes'
```
### Testing
Parsed the updated file with js-yaml 5.x semantics (warnings-as-errors): **0
warnings**, and the loaded config is deep-equal to the original across all 25
labels.
--
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]
