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

<@U040GU8DAR5> that’s for the 1.0x version of awsx, you need to update for that
`npm install @pulumi/awsx@v1.0.0-beta.11`

note: there are breaking changes between `awsx@0.40` and `awsx@1.x`

Is the resource coverage much lower in 1.0?

That’s a lot of breaking changes ser :sweat_smile:

Where did you find the list of breaking changes?  This?

<https://www.pulumi.com/docs/guides/crosswalk/aws/#upgrading-from-an-old-version-of-pulumi-crosswalk-for-aws>

yep, semver change :slightly_smiling_face:

I didn't see anything called out in the CHANGELOG, is there a list anywhere?

<https://github.com/pulumi/pulumi-awsx/blob/v1.0.0-beta.11/CHANGELOG.md>

Or is it a "everything is broken, read how to use the new resources and rewrite your declarations"?

I don’t know if we’ve defined a migration strategy yet

Is it worth moving towards 1.0.0 sooner than later as a consumer?

we will maintain awsx 0.40.x as `awsx-classic` but it won’t receive any functionality updates

If you want to keep components working using the pre V1 code, all the old components live in `/classic` . These won't receive updates to functionality going forward though. But that should let you upgrade individual resources when you're ready

I noticed pulumi has to download a couple of plugins when running the `pulumi up` command against the `v1.0.x` version of `awsx`

Would the pulumi GitHub workflow be compatible with the latest version `awsx`?