-
Notifications
You must be signed in to change notification settings - Fork 418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
found unexpected type for label 'xxxxxxxx' (should be array of config options) #710
Comments
Hello @danielmayor! Yes, you are right, this failure is related to the new major release. You are using the To mitigate the issue, please read the action documentation to find out how to adapt your configuration files for use with the new action version or use |
I would tend to say that the documentation is not correct. I'm running into the same problem mentioned in the description, having the following labeler configuration (please note that I tried different variations) terraform:
- changed-files:
- any-glob-to-any-file: terraform/** Which to me looks similar to the following snippet from the documentation mentioned above Documentation:
- changed-files:
- any-glob-to-any-file: docs/* The workflow definition is also similar to what I've seen in the documentation ---
name: Pull Request Labeler
on:
pull_request_target:
jobs:
triage:
name: Label triage
permissions:
contents: read
pull-requests: write
runs-on: ubuntu-22.04
steps:
- uses: actions/[email protected]
with:
sync-labels: true Am I missing something? |
Hello @HorizonNet! |
@MaksimZhukov Sure. Created #712. |
Description:
Somehow, today the labeler action started to fail. I didn't change any labeler config file or setup. I wonder if it's because of the new release (v5.0.0).
Execution output:
.github/labeler.yml:
Platform:
Runner type:
Repro steps:
The action runs automatically every time I create a PR. The
labeler.yml
hasn't any changes.Expected behavior:
Action should run successfully.
Actual behavior:
I get this error:
Error: Error: found unexpected type for label 'frontend' (should be array of config options)
The text was updated successfully, but these errors were encountered: