ci: change updater PR strategy to update #3780
Conversation
The default (which was the previous behaviour when the udpater was created) creates new branch & PR for every release. The "update" strategy updates a single PR per dependency.
|
Not sure I get this. Why does this matter? So what problem does changing to update strategy solve? |
less maintenance when you need don't want to merge a dependency yet but need to wait for another release. Also applies when you just don't care about the update because it doesn't change anything for the consuming SDK. You can leave the PR open and it will get updated the next time there's a release on the dependency, instead of creating multiple PRs, one for each version. |
Ahhh, I see. Cool, thanks @vaind ! |
The default (which was the previous behaviour when the udpater was created) creates new branch & PR for every release.
The "update" strategy updates a single PR per dependency.