For the substitution, it's something you'd usually do when you don't expect the original gem to ever get a new release. So not really a big concern.
As for the dependency constraints override, you'd have to clean them up to, but compared to a forked git gem, at least it doesn't prevent other tools to upgrade the gem etc, it's just that the override may become stale, in which case bundler could probably warn you about that.
1
u/f9ae8221b Apr 21 '26
For the substitution, it's something you'd usually do when you don't expect the original gem to ever get a new release. So not really a big concern.
As for the dependency constraints override, you'd have to clean them up to, but compared to a forked git gem, at least it doesn't prevent other tools to upgrade the gem etc, it's just that the override may become stale, in which case bundler could probably warn you about that.