Label automation unreliable for bridged provider updates

[guineveresaenger]

Automatic labels for provider upgrades have been failing over the past few days(?) in places.

Examples

• Upgrade terraform-provider-civo to v1.1.3 pulumi-civo#640 - author is pulumi-bot
• Upgrade terraform-provider-dbtcloud to v0.3.21 pulumi-dbtcloud#168 - author is guineveresaenger

The task is:

• verify that every provider's latest upgrade PR has a corresponding release.
• cut a corresponding release via release-bot if it does not
• find a root cause for what happened

Bridged Providers

Tier 1

• aws
• gcp
• azure
• azuread

Tier 2

• aiven
• akamai
• alicloud
• archive
• artifactory - Manual build here: https://github.com/pulumi/pulumi-artifactory/actions/runs/11729875175
• auth0 - Upgrade terraform-provider-auth0 to v1.7.3 pulumi-auth0#687 did not add label -manually kicked off patch https://github.com/pulumi/pulumi-auth0/actions/runs/11729670924
• azuredevops
• civo Upgrade terraform-provider-civo to v1.1.3 pulumi-civo#640 did not add label - manually kicked off patch https://github.com/pulumi/pulumi-civo/actions/runs/11729719769.
• cloudamqp
• cloudflare
• cloudinit
• confluentcloud
• consul
• databricks
• datadog
• digitalocean
• dnsimple
• docker
• ec
• external
• f5bigip
• fastly
• github
• gitlab
• hcloud
• http
• ise
• kafka
• keycloak
• kong
• libvirt
• linode
• local
• mailgun
• meraki
• minio
• mongodbatlas
• mysql
• newrelic
• nomad
• ns1
• null
• oci
• okta
• onelogin
• openstack
• opsgenie
• pagerduty - Upgrade terraform-provider-pagerduty to v3.17.0 pulumi-pagerduty#650 did not add a label and did not get shipped. Author is pulumi-bot. Manually kicked off minor build here: https://github.com/pulumi/pulumi-pagerduty/actions/runs/11730255191
• postgresql
• rabbitmq
• rancher2
• random
• rke -this one is interesting because the upgrade PR was merged in the same timeframe as the other stuck ones. Possibly due to order of issues closed?
• signalfx
• slack
• snowflake
• splunk
• spotinst
• sumologic
• tailscale
• tls
• vault
• venafi
• vsphere
• wavefront
• harness
• junipermist

[guineveresaenger]

Summary:

• The following four providers did not automatically receive a needs-release/ label on their upgrade PRs:
  • Artifactory
  • Auth0
  • Civo
  • Pagerduty
• All of these happened in the last two days
• All of these had duplicative pull requests that were manually closed. The duplicative issues were due to a refactor in ci-mgmt which has since been addressed. Theory: Having pull requests with exactly the same title confused label setting.
• Authorship seems irrelevant (pulumi-bot vs manual)
• Today's upgrade PRs are receiving needs-release/ labels again.

The missing releases have been run manually. This resolves the p0.

Closing this issue as the p0 was addressed and new instances of this behaviour are not observed.

[pulumi-bot]

Cannot close issue:

• does not have required labels: kind/, resolution/

Please fix these problems and try again.