This will be fixed in a pending release

It is indeed a bug that was introduced :/

This shouldn’t have broken anything though

Unless you were using a Pulumi cli version pre 2.25.0

2.22

I suppose upgrading a dependency is the bit that I'm worried about. What's the recommended syntax for the github action version to remain consistent with pulumi versions, but also opt-in to security/bug fixes?

so the issue you faced here (which wasn't well communicated on our part) is that the automation API is technically preview at this monent, so in order to get us to GA for it, we've been adding backward incompatible features with the CLI. We are now finished with that Upgrding the CLI should not force any dependency upgrades to your applications unless the Automation API requires a specific version. If you need to guard against upgraded CLI versions then you can change your CLI installation as follows:

- name: Install pulumi
  uses: pulumi/action-install-pulumi-cli@v1.0.2
  with:
    pulumi-version: 2.22.0

This is definitely the safest way for you to opt-in to changes

I definitely agree that this was unexpected behaviour

Also, just 1 more point, the action doesn't require/depend on the alpha, it's using a semver range to make the 2.25.0-alpha to be the minimun expected here

that's what we had, it failed at pulumi up as part of

pulumi/actions@v2

we will make sure and let any version changes be well communicated inadvance going forward here as it's definitely a pain 😕

i.e. we install

2.22.0

but then could run the actual up command as the installed version didn't meet the spec.

you can pin to a specific pulumi/action in the same way 🙂 We should also make that more visible for our users

if there is a commitment going forward that

pulumi/actions@v2

won't require a cli upgrade, then we're good.

there's no commitment on that while Automation API is in Preview

when it gets out of preview there will be

we don't want to pin an old version of the action, as we'll be opting out of critical updates right?

there's a balance that I get, but we realistically need a channel that is "stable with security and other critical updates" that doesn't require those kind of upgrades.

I'd suggest pinning then

i.e. forcing a minor cli version upgrade. Happy to cope right now, it's more about when this flux is over.

there's no way to do both

so we can't pin a minor version? we have to pin all the way to hotfix version?

you can pin a minor perfectly

what's the syntax for that?

2.25

throws an error on install.

2.25.0

there's no tags for minors only

won't that pin to

2.25.0

, as in it won't take

2.25.1

automatically?

correct

and.25 is the minor version

we dont publish tags for patches unless we require them