Closed radekmie closed 1 year ago
The big change is the replacement of mgo with the official mongodb driver. This is work that had been done in vlasky/oplogtoredis.
This isn't an incompatible change, as far as meteor compatibility is concerned, but would merit some testing for your particular environment (your mongo + redis version, etc) before deployment, just to make sure that the libraries are still compatible with your redis/mongo versions.
The automated regression testing is targeted at mongo 4.4 and redis 6.0.
Thanks for the answer! So if we wer'e still at MongoDB 4.4 we can simply update the version and that's it? (With a huge dose of testing, of course, but no config changes, etc.)
I can confirm that we're using v2.0.0 in production for a while now and it looks like everything works with MongoDB v4.4.
We're using v1.2.0-beta.1 in production for a while now (actually, not that long after it got released), and it really works for us well (even while being hammered with a lot of writes)! I was extremely happy to see that there's some movement in here, and the new release, but there's no information on what changed or whether there are any breaking changes. The bump of the major version suggests some, but maybe that's not the case?