Error unknown command do for dagger (version 0.3.6) | Dagger | Page 1

cyan quartz Dec 1, 2022, 3:24 AM

#

Hi there!
It seems that the "do" command has stopped working in the 0.3.6 environment released today.
How should I change it? Or is there an upgrade guide?

this is the script we are using now.

Github Actions yml

- name: dagger run rubocop
  uses: dagger/dagger-for-github@v3
  with:
    cmds: do rubocop

CUE

rubocop: {
  run: bash.#Run & {
    input: deps.output
    workdir: "/srv"
    script: contents: #"""
      rubocop
      """#
  }
}

wanton anchor Dec 1, 2022, 4:55 AM

#

hey @cyan quartz! we released a new CLI today which has some breaking changes and seems like we missed the github action. If you add a version (https://github.com/dagger/dagger-for-github#inputs) to your action with v0.2.36 I think that should fix your problem 🙏

#

our apologies for the inconveniences

cyan quartz Dec 1, 2022, 5:36 AM

#

hey @wanton anchor !
Thanks, fixed now! 😄

I'm hoping to upgrade sometime soon.
Can I see the breaking changes and upgrade guide?

flat nacelle Dec 1, 2022, 7:13 AM

#

@wanton anchor should this be added to the FAQ or is it something we will fix in the action itself / action documentation / somewhere else? FYI https://docs.dagger.io/162770/faq#ive-upgraded-to-the-latest-dagger-cli-and-my-cue-plans-no-longer-work-why /cc @spring marsh for visibility and input

wanton anchor Dec 1, 2022, 3:09 PM

#

flat nacelle <@336241811179962368> should this be added to the FAQ or is it something we will...

this is something it should be fixed in the action so it uses the new dagger-cue binary. I'll open an issue for that

#Error unknown command do for dagger (version 0.3.6)