mongoid

We're just trading anecdotes at this point but I can't say I've encountered the same problems over the past decade of working with it. That's generally because of limiting dependencies, but also because it's a good idea to peek at the changelog or release notes when bumping the minor or major version. TFA doesn't mention or acknowledge this aspect of the issue, but it did surprise me that they considered a version bump from 7.0.8 to 7.3.3 to be innocent looking. In fact, these 'minor' releases actually appear to be quite significant and the issue in question in TFA was explicitly documented. [0][1] I hate to say it but this was just a case of sloppy work on the startup's part. It took me less than 5 minutes to find that info. [0] https://docs.mongodb.com/mongoid/current/tutorials/mongoid-u... [1] https://github.com/mongodb/mongoid/release

The mongoid repository (https://github.com/mongodb/mongoid) doesn't have issues turned on and instead points people to JIRA. That's one way to avoid users reporting issues like this - I'd see JIRA and "nope" right out.

The changelog for 7.1 (https://github.com/mongodb/mongoid/blob/master/docs/release-...) even explicitly call this out as a breaking change: Breaking change: In Mongoid 7.1, when condition methods are invoked on a Criteria object, they always add new conditions to the existing conditions in the Criteria object. Previously new conditions could have replaced existing conditions in some circumstances. Ironically they also have a breaking change in 7.1.1, so they just don't give a fuck at all.