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

<https://github.com/pulumi/pulumi/issues/2318> will be available before 4.0, in fact the experimental preview for it will be in the _next_ release!

great! there are some other features we are interested in that are part of 4.0. do we have timelines on this?

I don't know the timelines for 4.0 sorry.

<@U015BDQ9HJ5> which other features in 4.0 are you interested in?

<https://github.com/pulumi/pulumi/issues/2247|https://github.com/pulumi/pulumi/issues/2247> but I believe there is a workaround where we can explicitly configure automatic refresh: <https://github.com/pulumi/pulumi/pull/8071|https://github.com/pulumi/pulumi/pull/8071> we were also looking forward to <https://github.com/pulumi/pulumi/issues/2307|https://github.com/pulumi/pulumi/issues/2307> but i just noticed that is has been removed. 

I think hierarchical configs don’t have to be a breaking change, so it can be tracked independently of 4.0. We want to use 4.0 mostly for breaking changes, and keep shipping all non-breaking features in minor versions.