This message was deleted.

What exactly did you have in mind?

same as the Pulumi core provider do: https://github.com/pulumi/pulumi-cloudflare/blob/master/.github/workflows/check-upstream-upgrade.yml

I dont't think that all pulumiverse providers are ready to be upgraded using ci-mgmt. And I doubt that every pulumiverse provider needs all those GitHub workflows (see screenshot). Both providers that I maintain two small workflows: one to verify that a PR can be build and adhere to linting rules. And one to publish a new provider version. As I said, personally, I don't think the mass of workflows that are used for the providers maintained by Pulumi are required for Pulumiverse providers.

I am not working with

ci-mgmt

with the providers I maintain. But I liked the notification in Slack, when a new TF version is available.

Oh, so misunderstanding on my side, sorry. Yep that would be great!

To automatically post in a channel here, we need help from an admin to get it set up at least.

Wouldn't it not better to have an issue created in the respective Pulumiverse provider when the upstream TF provider has been updated instead of having a message posted here in the Slack channel?