v1.0.25: deploy silently no-ops — prints 'Using vendor/bin/dep' then exits without running any tasks

[mglaman]

Description

After the v1.0.25 release, the action prints Using "vendor/bin/dep". and then exits immediately with a success code without running any Deployer tasks. No error is shown, no Deployer output is produced.

Steps to reproduce

Use the action with a standard vendor/bin/dep setup:

- uses: deployphp/action@v1
  with:
    private-key: ${{ secrets.PRIVATE_KEY }}
    dep: deploy stage=uat --ansi -vvv

Expected behaviour

Deployer runs and streams full task output (deploy:info, rsync, artisan:migrate, etc.)

Actual behaviour

The action prints Using "vendor/bin/dep". and immediately returns success. No tasks run, nothing is deployed.

Evidence

Two runs on the same day against the same branch and host:

v1.0.24 (SHA 5d9b48b8) — working: full Deployer output, release created on the server.

Using "vendor/bin/dep".
$ php vendor/bin/dep deploy stage=uat branch=main --ansi -vvv  --no-interaction --ansi -v
[...] task deploy:info
[...] task deploy:setup
[...] task deploy:lock
...

v1.0.25 (SHA 9229ee26) — broken: no output after the first line.

Using "vendor/bin/dep".
[immediately jumps to next step]

v1.0.25 was released at 19:37 UTC on 2026-04-07. The broken deploy ran at 21:03 UTC the same day; the working deploy ran at 13:01 UTC the same day using v1.0.24.

Workaround

Pin to the v1.0.24 SHA:

- uses: deployphp/action@5d9b48b8ce6a81cfff681cbc330eb7944f102093

Environment

• deployphp/action v1.0.25 (SHA 9229ee2680f070f60c53cf62af15c8317a03a0b8)
• deployer/deployer v7.5.12
• Runner: ubuntu-24.04

[Seb33300]

On my side, deployment is still working, but I no longer have any details printed in the deployment logs.

[Seb33300]

Just realized. On my side it's still working with Deployer 7 but not with Deployer 8

[shockbytes]

Same for me. I downgraded to v1.0.24 and it just works fine.

[antonmedv]

Please test if master solves the issue.

[RenautMestdagh]

Having the same issue in v1.0.25. Changing version to master solves the issue for me.

[alexisLefebvre]

I skipped v1.0.25 because of this report, I’m not sure if it would have been "broken" for me, but I had no issue to deploy with v1.0.26.

[jordyvanderhaegen]

@antonmedv can you bump v1 to point to the same commit as v1.0.26? This currently still points to v1.0.25

[antonmedv]

done!