blobwave I’ve archived https://github.com/pact-foundation/sucker_punch We were using our fork as we waited for https://github.com/brandonhilkert/sucker_punch/pull/253 to be merged. In an ideal world I would prefer to delete the fork, however we have released gems that contain this reference, to our fork, so I would imagine they would then break. We have updated versions of the gems published that use the now updated, release, origin package. https://github.com/pact-foundation/pact_broker/commit/b1bac7118ab782672d51b1c0f36240771d7e3156

How old are the gems? Should we set ourselves a remind for when it's been 'long enough' that we can delete the fork?

between march 23 and feb 24, pact broker gems were released with a dependency on our forked suckerpunch gem. any using older versions, will be fine as long as they are running ruby 2.7 or earlier. my worry is the gems released in that 13 month period will effectively be unresolvable and I’m not sure if bundler would be okay with that. might be a non issue but I haven’t found much in the way ont internet to ascertain what may happen or best practise here

Fair, and given how relatively recent that is, I would also err on keeping the repo archived for now. Perhaps once 24 months have elapsed, then it might be safe to delete the repo 🙂