https://pulumi.com logo
Title
g

green-musician-49057

04/20/2021, 2:48 AM
Is anyone else getting this error in their github actions CI/CD pipeline?
Error: Major version mismatch. You are using Pulumi CLI version 3.0.0 with Automation SDK v2. Please update the SDK.
I checked the pulumi/actions repo and it seems like you're getting the same error: https://github.com/pulumi/actions/runs/2385713822 UPDATE: We fixed this by pinning the version of the pulumi action, e.g.
uses: pulumi/actions@v2.2.0
We're using v3 of the Pulumi SDK. Not sure how we would upgrade to v3 of the Automation SDK, but I think that version is referring to the action itself?
a

adventurous-garage-59192

04/20/2021, 3:22 AM
Can confirm, just started getting the same issue. Was the action version suppose to be bumped as well? The Pulumi v3 requirement has rolled out to
pulumi/actions@v2
consumers.
g

green-musician-49057

04/20/2021, 3:27 AM
UPDATE: We fixed this by pinning the version of the pulumi action, e.g.
uses: pulumi/actions@v2.2.0
r

red-match-15116

04/20/2021, 3:35 AM
Hey folks! It was not intended that this would be pushed to consumers before we did the
v3
release.
So, just for my own understanding, if you don’t pin the action version it appears it pulls in what’s in the main branch in the action? That’s pretty wild. I would’ve thought it would pull the latest released version.
f

flaky-ghost-73674

04/20/2021, 3:37 AM
I believe that’s right. Actions generally recommends (and will produce templates that) pin to a specific tag with the
@[tag]
syntax, but if you don’t provide one I think it takes latest from the default branch.
g

green-musician-49057

04/20/2021, 3:39 AM
For what it's worth, we had it pinned to @v2
r

red-match-15116

04/20/2021, 3:47 AM
So I think there are 2 issues here: 1. @green-musician-49057 it sounds like you want the action to be
v3
so you can use the
v3
CLI because your code is using automation api from SDK
v3
- is that right? 2. @adventurous-garage-59192 can you tell me more about the issue you’re running into? Are you getting the same error? And you’re using CLI v2?
g

green-musician-49057

04/20/2021, 3:50 AM
We were not using the automation API, and we were on pulumi sdk
v2.24.1
the first time the issue cropped up, about 3 hours ago, 6:02PM PDT
r

red-match-15116

04/20/2021, 3:52 AM
Right, but the error says that you’re using CLI v3 - is that true?
You are using Pulumi CLI version 3.0.0 with Automation SDK v2. Please update the SDK.
g

green-musician-49057

04/20/2021, 3:54 AM
we were using whatever is installed from this action:
pulumi/action-install-pulumi-cli@v1.0.1
No
pulumi-version
specified. I assume that would try to install the latest, which would be v3
👍🏽 1
r

red-match-15116

04/20/2021, 3:55 AM
Yeah, I that action installs
latest
if no version is specified. You can specify the version with:
- name: Install pulumi
  uses: pulumi/action-install-pulumi-cli@v1.0.2
  with:
    pulumi-version: 2.25.1
a

adventurous-garage-59192

04/20/2021, 4:23 AM
Pinning the CLI version fixed the issue, thanks! I guess the problem is in the opposite direction than I assumed, with a new version of the action that supports v3 not being published yet. Will update my pulumi stacks when it is!
b

billowy-army-68599

04/20/2021, 5:16 AM
hey sorry about this, we have a newly released version of the Pulumi action using the latest major version - it's highly recommended you pin to major versions in any case, but hopefully this should fix your CI pipelines! Sorry for the disruption