Rollback breakage caused by Dagger CLI 0.3 release
shykes opened this issue · 3 comments
Problem
We recently released a new Dagger CLI, version 0.3, which is a hard breaking change from 0.2. There is a migration path in preparation (using a new CLI called dagger-cue
which is drop-in compatible with 0.2), that was meant to be rolled out soon.
But we accidentally broke users of the current github action now, without warning, by auto-updating this action to dagger 0.3. This should be immediately reversed regardless of future migration plans.
Solution
Change the latest version of this action @v3
to pin to dagger
0.2, instead of latest.
This should resolve the immediate issue for users of the Github Action, and allow us to finish planning a proper migration path.
Thank you @fredleger for alerting us and we apologize for the poor experience!
Hey @fredleger! Can you confirm that the latest dagger/dagger-for-github@v3
fixes your issue?
FWIW https://github.com/dagger/dagger-for-github/releases/tag/v3.2.0
I just roll backed my changes from this morning, and it's working like a charm 🎉
Now i'm just waiting for asdf plugin for dagger-cue to test the dropin replacement of previous dagger cli on my laptop :-)
Thanks for the follow up
Sure thing! Thanks for the quick reply 🏎