Francois L

@sethvargo All the packages listed in your link seem to be installed in a workflow running on `ubuntu-latest`. The current workaround is to add this line prior to the 'gcloud...

Hi, I am noticing the exact same issue. Any development regarding this?

Just noticed this problem this morning on my windows machine (ubuntu 20.04 wsl2) while I had no issues before. ``` $ docker --version Docker version 20.10.6, build 370c289 $ docker-compose...

duplicate of #1665

Just got a similar error using `opsless/[email protected]` Not sure if it matters but the workflow in question is triggered by a con job: ``` name: Test demos on: schedule: -...

Since the workflow is also configured with `workflow_dispatch`, I triggered it manually and did not get the above Action error

@Spartakovic you are right :) no need to specify if digger is going to parse it anyways...

Correct, just updated the title/description for this feature request.

As it turns out, it seems like it's already the default behavior, except for the fact that when using a mono-repo , the workflow will currently continue when a project...

To add-on to my last comment, now that digger combines multiple plan outputs into a single comment, the fact that the workflow is not failing when a lock can be...