This message was deleted.

We definitely can't have our own Pulumiverse setup here. First because it is too much work, second because we would always be behind the upstream setup that the Pulumi engineering team has. Looping in @orange-policeman-59119 here, as it is a long standing personal aim to have https://github.com/pulumi/ci-mgmt reusable for third parties.

It would be good to have an issue tracking this so that it can be prioritized; I think the long-term direction ought to be less that the workflows are synchronized from ci-mgmt, and more that the logic moves into some specific maintained GitHub Actions, such as: • https://github.com/pulumi/upgrade-provider • https://github.com/pulumi/pulumi-package-publisher

@orange-policeman-59119 The idea to have any kind of GitHub action instead of workflow templates which are indeed harder to maintain automatically sounds logical. But who would be in charge to add an issue so that the demand from Pulumiverse could be tracked?