This is what separates teams that scale from teams that survive:

Teams that scale prioritize continuous dependency updates, whereas those that survive tend to batch updates into quarterly sprints, leading to higher risks of CVEs and supply chain incidents. This batch update model can result in multi-day incidents due to large version jumps and changelogs. To avoid this, teams should adopt a continuous update model with smaller, more manageable changes. This approach reduces the risk of incidents and allows for faster recovery. It's essential to treat dependency updates as reliability work, not maintenance work.