Create upgrade labels when necessary

iwahbe commented 9 months ago

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

When an upgrade is indicates, upgrade-provider needs to apply the label to trigger the upgrade on PR merge. Labels added are needs-release/patch, needs-release/minor and needs-release/major.[^1] If label does not exist on the provider and needs to be created, the upgrade fails: https://github.com/pulumi/pulumi-rke/actions/runs/6935929271/attempts/1.

We should solve this by:

Standardizing the list of provider labels and making sure the release labels are included, or
Creating the labels if they don't already exist within upgrade-provider.

Affected area/feature

iwahbe commented 9 months ago

The same issue just blocked https://github.com/pulumi/pulumi-spotinst/actions/runs/6946256008/attempts/1.

iwahbe commented 8 months ago

The urgency here is very low, since this was resolved upstream by https://github.com/pulumi/ci-mgmt/pull/757.

ringods commented 4 months ago

This issue makes upgrade-provider not usable outside of Pulumi.

https://github.com/pulumiverse/pulumi-acme/actions/runs/8778868034/job/24085996153#step:2:661

iwahbe commented 4 months ago

I'll take a look here. As with all of our partially internal tools, we need to create a clear distinction between what needs a pulumi specific setup and what should be usable in any repo.

pulumi / upgrade-provider