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

Removed, re-ran `npm install`, same warning.

I was suggestion other way around :slightly_smiling_face: commit lock file and use it with `npm ci`, this way any changes on pulumi side wont affect you until someone manually refreshes it, but then if there are problems it is easy to revert to a working lock

Oh, yeah, I'm always committing `.lock` files, only this happens with new projects. :slightly_smiling_face:

copy it from old ones :slightly_smiling_face:

That's not really a solution... :slightly_smiling_face:

agree, more like a workaround until Pulumi org sorts it out

Well, ended up upgrading all `pulumi` packages to `1.0.0-beta.1`.

The latest CLI release has a change that will avoid warning on this combination of packages.  If you do need to use a mix of `0.x` and `1.0.0-beta.x` versions - you can do so with the latest CLI.

@pulumi/random has no 1.0.0-beta.x yet :disappointed: