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

Regarding awsguard, why is the npm package `0.3.0` , but in GitHub it’s unreleased? <https://www.npmjs.com/package/@pulumi/awsguard> <https://github.com/pulumi/pulumi-policy-aws/blob/master/CHANGELOG.md> ?  Also, this upgrades dependency MAJOR versions, I don’t think this should be released as a MINOR.  It caused breaking changes <https://github.com/pulumi/pulumi-policy-aws/commit/5b34b8fb4e10020052528d42643f72f96cbae597#diff-cc5a2f170768969f124108ad3be7fdbcbed774c11774d99a87a3a78fef4ab97bR13-R15|https://github.com/pulumi/pulumi-policy-aws/commit/5b34b8fb4e10020052528d42643f72f96cbae597#diff-cc5a2f170768969f12410[…]d99a87a3a78fef4ab97bR13-R15>

Hi <@U013Q0AKUCW> that’s just a missing push on the changelog - the tag is there for 0.3.0

<https://github.com/pulumi/pulumi-policy-aws/releases|https://github.com/pulumi/pulumi-policy-aws/releases>

WRT it being a major change, you are correct but semver allows that as the library is &lt;1.0.0, breaking changes can be shipping as a new minor version

We’ve done the same when publishing the updated awsx and eks

I’m sorry this caused breaking changes for you :/ 

That was not intentional to cause any upgrade pain