Hello Community. We are deploying a forked version...
# troubleshoot
w
Hello Community. We are deploying a forked version of datahub (only minor changes) and after a long period of inactivity we are doing an update from 0.8.35 to 0.10.0. When we develop our fork, we tag our own releases with our own git tags that don't follow the exact format
vX.Y.Z
that the regular datahub code does. Up until now that hasn't mattered a lot since that value was mainly used in the UI to show the version running. But it seems that recently this value has become more important, controlling a step in the bootstrap process. I'm wondering if anyone else have encountered this and how you chose to deal with it. Best Regards
✅ 1
a
Hi Thomas, this is likely due to us introducing another digit to our feature releases for patches and minor updates, @orange-night-91387 may be able to help you out here
o
Hiya! As long as you tag all components the same, it shouldn't cause issues. The crux here is that it puts a version compatibility requirement between components, rather than enforcing a particular format. So as long as you tag datahub-upgrade, the consumer apps, and gms with the same version tag you should be fine here. If you're releasing them with different versions then that's how you'd run into problems.
w
Yup. I see that now. Thanks Ryan.