Prior to this change, all provider releases via this tool only occurred on upstream upgrades. This meant that security and codegen/bridge updates would merge to the default branch, but wait on an upstream release to apply to the provider, potentially resulting in a provider using an ancient version of the bridge.
This pull request sets a maximum ~8-week release cadence for all providers.
During a bridge update, we check if we have released the provider in question within the last 8 weeks.
If we have not, and the upgrade is a non-upstream upgrade, we will add a needs-release/patch label to the bridge update pull request.
Doing this will result in more frequent upgrades, ensuring our providers use a recent bridge and pulumi version.
One detail to call out:
We may choose to set the release cadence to 7 weeks, to ensure we "catch" the update at minimum every 8th week; this PR sets it to 8 weeks exactly.
We can also count actual bridge releases if we do not want to use time comparisons.
Prior to this change, all provider releases via this tool only occurred on upstream upgrades. This meant that security and codegen/bridge updates would merge to the default branch, but wait on an upstream release to apply to the provider, potentially resulting in a provider using an ancient version of the bridge.
This pull request sets a maximum ~8-week release cadence for all providers.
During a bridge update, we check if we have released the provider in question within the last 8 weeks. If we have not, and the upgrade is a non-upstream upgrade, we will add a
needs-release/patchlabel to the bridge update pull request.Doing this will result in more frequent upgrades, ensuring our providers use a recent bridge and pulumi version.
One detail to call out:
Fixes https://github.com/pulumi/ci-mgmt/issues/726.