Linter returns this error
.github/workflows/deploy-project.yml:34:7: unexpected key "queue" for "concurrency" section. expected one of "cancel-in-progress", "group" [syntax-check]
|
34 | queue: max
| ^~~~~~
Full context
env-prod:
concurrency:
group: ${{ github.ref }}-${{ inputs.project-tag }}-prod
queue: max
name: prod
relevance documentation stating this is correct syntax
https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency#example-queueing-multiple-pending-runs
To allow more than one pending job or workflow run to wait in the same concurrency group, use the optional queue property. The queue property accepts the following values:
single (default): At most one job or workflow run can be pending in the concurrency group. When a new job or workflow run is queued, any existing pending job or workflow run in the same group is canceled and replaced.
max: Up to 100 jobs or workflow runs can be pending in the concurrency group. When the queue is full, any additional jobs or workflow runs are canceled.
The combination of queue: max and cancel-in-progress: true is not allowed and will result in a workflow validation error.
Linter returns this error
.github/workflows/deploy-project.yml:34:7: unexpected key "queue" for "concurrency" section. expected one of "cancel-in-progress", "group" [syntax-check]
|
34 | queue: max
| ^~~~~~
Full context
env-prod:
concurrency:
group: ${{ github.ref }}-${{ inputs.project-tag }}-prod
queue: max
name: prod
relevance documentation stating this is correct syntax
https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency#example-queueing-multiple-pending-runs
To allow more than one pending job or workflow run to wait in the same concurrency group, use the optional queue property. The queue property accepts the following values:
single (default): At most one job or workflow run can be pending in the concurrency group. When a new job or workflow run is queued, any existing pending job or workflow run in the same group is canceled and replaced.
max: Up to 100 jobs or workflow runs can be pending in the concurrency group. When the queue is full, any additional jobs or workflow runs are canceled.
The combination of queue: max and cancel-in-progress: true is not allowed and will result in a workflow validation error.