Ask HN: How do you keep up with changes to open source deps. We use a lot of open source code and it changes a lot, we try to stay current by updating dependencies on roughly a half-year cadence. Most of the time we are able to catch any regressions before they hit production but there's a few that always make it through. We've been discussing implementing some more structured way of reviewing changes to external dependencies, perhaps assigning individuals/teams to watch a dependency and review any changes as they come in. I'm curious to hear HN's thoughts, how have y'all been dealing with changes to external dependencies? any approaches that you'd recommend? |