A minor version change introduced a breaking change

[nassud]

I recently upgraded from mongoose 8.2.0 to 8.12.2. Unfortunately, this update included a breaking change introduced in version 8.10.0.

I was under the understanding that mongoose follows the Semantic Versioning system (Am I wrong?)

Why release a breaking change as a minor update?

[vkarpov15]

This isn't a breaking change, more of a bug fix. MongoDB doesn't support multiple operations in parallel within a single transaction, so create() with multiple docs in a transaction without ordered: true would cause a transaction error unless the create() happened to be the first operation in the transaction.

[nassud]

Thank you so much Valeri for explaining. Unfortunately it was a breaking change in my case. As simple as it wasn't failing and changing the minor version started failing. AKA breaking. If the bugfix changes the behavior by throwing an error that wasn't there before. My end goal was to let you guys know. I appreciate what you guys do. Thank you.

…

On Mon, Mar 31, 2025, 12:00 Valeri Karpov ***@***.***> wrote: This isn't a breaking change, more of a bug fix. MongoDB doesn't support multiple operations in parallel within a single transaction, so create() with multiple docs in a transaction without ordered: true would cause a transaction error unless the create() happened to be the first operation in the transaction. — Reply to this email directly, view it on GitHub <#15334 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQ6JYY73JG4HDKY4AGBA3D2XFYD7AVCNFSM6AAAAAB2ABZH6KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRXHEZDGMY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[vkarpov15]

That's fair, and I'm sorry for the trouble. Sometimes the line between bug fix and breaking change can get a bit blurry, and it was in this case, which is why we put this behind a minor release rather than a patch. Unfortunately your tests were passing because they relied on behavior that the MongoDB server does not support, so they worked more by accident than by design. Again, sorry for the inconvenience.