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

im building this all in a docker container, i think i'll need to build it "nocache" each time to get the latest version of the binary,  and also move my package to read `^3.0.0` to match the dependency of the pulumi/aws package and build the whole thing at once each time to make sure they're all on same version

we have this a lot, the clue for us is to make sure we remove and regenerate the lock file. especially when using stuff like renovate/dependabot

as soon as there is any pulumi package that is updated

thanks for that!  yea, rebuilding all on the same basic version requirement from scratch got them all on the same line.. weird one