You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider adding a checklist item to pay special attention to Dependabot PRs on the day of the release (and investigate any failures before cutting the release). Otherwise release wranglers may not notice Dependabot failures until after cutting the release (and Dependabot could have already caught the breakage, but it went unnoticed).
The text was updated successfully, but these errors were encountered:
🤔 Isn't monitoring Dependabot PRs the whole of the 2-week sprint already a task for the release wranglers? Theoriticaly, the previous-release wranglers will notice the red Dependabot PRs before the next-release wrangling is commencing, no? Apologies if I'm missing some part of the current process.
While monitoring Dependabot is already part of release wrangler duties, it's something that can easily be left to after cutting the release and that's what happened 1.63.0. If the release checklist had prompted us to check Dependabot's PRs for issues right before cutting the release, we would have had more options to better handle the situation.
Consider adding a checklist item to pay special attention to Dependabot PRs on the day of the release (and investigate any failures before cutting the release). Otherwise release wranglers may not notice Dependabot failures until after cutting the release (and Dependabot could have already caught the breakage, but it went unnoticed).
The text was updated successfully, but these errors were encountered: