No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<@U099VH4FCKT> Do you know how (Linux) Pulumi CLI decides when to report that its version is lagging behind the released version? I've just noticed that I'm on 3.166, but 3.190 is out. In the past I've reliably been kept within a couple of versions of latest by virtue of the console log message that includes the upgrade script(let). But not this time.

I only noticed it because I've added `packagemanager: bun` to some of my projects, and it's barfing with
&gt; error: installing dependencies: failed to parse options: packagemanager option must be one of auto, npm, yarn or pnpm, got "bun"

Interesting question, I had no idea but tracked down the <https://github.com/pulumi/pulumi/blob/ffcb32fdd086a305d6e6a9abfcf3f83f0d650efb/pkg/cmd/pulumi/pulumi.go#L670|code for this>. Looks like the message will be displayed at most once per day. Additionally if there is a `SKIP_UPDATE_CHECK` environment variable no message will be shown.

Thanks for looking into it. I don't have that variable set to anything, and my machine isn't configured weirdly (other than having an NZ timezone). No idea why I never got pinged about this.