renovate: disable rollbackPrs #149
Conversation
Not sure why but the config change in commit 8f61a71 caused us to now get rollback PRs for digest updates which is wrong and very noisy. Let's keep them disabled for now and let Chris figure it out when he is back. Signed-off-by: Paul Holzinger <[email protected]>
|
Successfully triggered github-actions/success task to indicate successful run of cirrus-ci_retrospective integration and unit testing from this PR's 0e134f92437bd091e71b4ab99242135977770703. |
|
confirmed containers/podman#18109 no longer shows planned rollbacks |
|
Finally catching up to this. As with #148 you did the right thing here under the circumstances. Rollbacks for golang have been basically broken for a long time now. The risk of getting one is probably low (though it has happened a few times), the complexity added to support SHA based updates (which we use a lot of) isn't worth it. The main concern is over security issues (they happen) and accidental/broken releases (they happen less). Major security issues should (eventually) have a vulnerability alert issued (which will open it's own PR). So really we only need to watch out for accidental/broken releases (conmon had one). Those can be worked around with other config. options (as we did with conmon). So overall 👍 nice job. |
Not sure why but the config change in commit 8f61a71 caused us to now
get rollback PRs for digest updates which is wrong and very noisy.
Let's keep them disabled for now and let Chris figure it out when he is
back.
@vrothberg @edsantiago PTAL again i.e. containers/podman#19206
This should not be created.