Breaking change to concurrency group syntax?

Hello!

This morning, one of my GitHub Actions workflows that I’ve had in place for a few weeks suddenly stopped working due to a syntax error in my workflow code. The workflow file itself hasn’t changed, and it really looks like either an issue with the workflow parser or a breaking change to the valid syntax.

Here is a sample of the syntax I’m talking about:

jobs:
  test:
    name: Test
    runs-on: [self-hosted]
    concurrency:
      group: ${{ github.ref }}
      cancel-in-progress: false

Specifically, the concurrency.group line is no longer recognized as valid syntax as of this morning. This is strange to me, because this has been working for a few weeks, and the official documentation for the workflow syntax seems to suggest that this should still be possible:

I have also tried the following values for concurrency.group, each of which also failed due to a syntax parsing issue:

  • ${{ github.head_ref }} (this is officially recommended in the docs as a working example)
  • test-${{ github.ref }}

Thanks in advance for any help, I am really not sure how to proceed with this now broken workflow.

25 Likes

Can confirm this also has just occurred for us. Same issue workflow file is no longer valid.

1 Like

I was just about to report the same issue - suddenly all our workflows are failing due to a syntax error, as the job.<id>.concurrency.group is no longer valid.

1 Like

Happens also on workflow-level concurrency group concurrency.group

2 Likes

Seeing this as well even with a static string group: testing

Strangely this appears to only be affect some of our repos

1 Like

Related: https://twitter.com/JamesKyburz/status/1466805012990939139

It seems to affect all workflows with concurrency, and some (push) events may trigger workflows that it should not.

2 Likes

Thanks everyone for the replies, it’s good to know that I’m not the only person with this issue :smiley:

1 Like

We’re seeing the same broken behavior here. Had to remove concurrency steps temporarily in our workflows until this is fixed.

1 Like

Same problem. I’ve removed concurrency from my workflow and it started working.

2 Likes

Same here. How do we report this to GitHub? There’s no outage showing on the status page.

1 Like

Same here (Merge pull request #21909 from mkouba/qute-parser-skip-param-debug-log · quarkusio/quarkus@52f3cc9 · GitHub), looks like someone was in a hurry for the weekend (quoted from @famod)

2 Likes
4 Likes

Same here! :wave: We believe that the problem is on our side :sweat_smile:

1 Like

Ditto for our entire organization. I just had to remove the concurrency section from 10 different builds and we still have a few dozen branches that are thrashing on the old value. I just finished cleaning up our build files too :frowning:.

1 Like

Maybe the public servers are running a version prior to 3.2 which was included the concurrency feature.

1 Like

The original issue I was facing no longer seems to be occurring - my workflow is functional again.

I’m going to leave this open to allow GitHub staff to confirm that the issue has been resolved.

4 Likes

Resolved for Apache Airlfow too.

2 Likes

Working for us as well.

Brought it back to my workflow and now it works as expected.