#dagger-for-github: Workflow fail after upgrade dagger-for-github from v8.2 to v8.3

1 messages · Page 1 of 1 (latest)

torn hazel
#

Solved 2026-03-04

I have encountered an issue with my GitHub workflows with dagger-for-github after upgrading from v8.2 to latest (v8.3).
The issue I am seeing is reported as https://github.com/dagger/dagger-for-github/issues/202

The issue seems to be multi line calls when using dagger-for-github

Here is a snippet from a workflow:

   - name: Build & push image
    uses: dagger/dagger-for-github@456fc3af63a2ba6f9789af9c55045b459115541b
     id: publish
     with:
       module: apko
       call: |-
        --repository cgr.dev/chainguard/apko \
        --tag latest \
        container

It does continue with more, but this is the crucial part.

When running this workflow it does fail at this call. It does show something similar to:

Run dagger/dagger-for-github@456fc3af63a2ba6f9789af9c55045b459115541b
Run set -o pipefail
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 6 100 6 0 0 14 0 --:--:-- --:--:-- --:--:-- 14
Installing dagger
Run # Determine if the user wants to execute a dagger command or just install
Run verb=call
verb=call
shell=$(echo '""' | jq -rj .)
dagger_flags=$(echo '"--progress plain"' | jq -rj .)
args=$(echo '""' | jq -rj .)
call=$(echo '"--repository cgr.dev/chainguard/apko\n--tag latest\ncontainer\n

and this continues as well, but the call there fails:

Error: Unable to process file command 'output' successfully.
Error: Invalid format '--tag latest'

This was run with v8.2 and fails with v8.3, without any other changes.

So it is something that has changed that causes this.

Looking in dagger-for-github repo I have not been able to locate the "Run verb=call" part.
Have looked into dagger repo as well.

Do anyone know where to look for this call code?

I did create the issue last week but have not received any attention yet.
And I have not seen anyone else having this issue either.

GitHub

What is the issue? Have used a modified v8.2.0: SHA d809c26 of dagger-for-github When trying to upgrade to (v8.3.0) SHA 456fc3a we get an error in the workflow part that seems to indicate that ther...