Go modules dependency rollbacks

Hello friends,

I am moving an old code-base from glide to go modules. We have this old script that’s ran by our CI that checks that none of our glide dependencies moved back in time following a new addition/upgrading. Indeed, we had noticed that this could happen and we wanted to get notified.

Is this behavior possible with go modules? Where for example running an update, or adding a dependency and such, can result in a pre-existing (potentially direct) dependency’s version rolling back? And if yes, do we have a tool to check for those instances?

Thank you for taking the time to read this!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.