alcaeus
commented
1 day ago There are a couple of points to consider here. First of all, the API is still compatible, i.e. we did not remove any methods, classes, or anything else you may have been using. What we did drop is connecting to a server version that has been unsupported for more than three years after announcing we'll do so, which we've done in multiple previous instances.
The second point is that you are relying on a transitive dependency here. You're depending on the Laravel integration, which in turn depends on the MongoDB driver. We are currently working on a 2.0 version of the driver, with the goal of having the Laravel integration support both 1.21+ and 2.0 at the same time. As long as there are no breaking API changes in the Laravel integration itself, this change will be released in a minor version according to SemVer guidelines. Extending from this thought, even if we had released this as part of a 2.0 release, we would still most likely have released a new minor version of the Laravel integration that works with this 2.0 release. Unless you had an explicit constraint on the driver itself, your problem would not have changed.
Furthermore, I'll note that MongoDB 3.6 was end-of-lifed in April 2021 in accordance with the MongoDB Software Lifecycle. Drivers support end-of-lifed server versions for 36 months, after which we may decide to drop support for them in order to remove legacy code and reduce maintenance. However, we do not consider this a breaking change, as we don't expect or recommend people are running a server version that has not received any support or security updates for three years. We will continue to drop support for such outdated server versions in future minor versions, most likely with dropping support for MongoDB 4.0 sometime after April 2025.
Last but not least, I'll note that you are using CosmosDB. Since the driver you are using was written for MongoDB, we cannot give any guarantees or offer any support for your use case, and even within a minor version you may see breakage from using the driver with CosmosDB. For more information on this, I'll direct you to our documentation or compatibility page.
ariddlestone
We compose this library into our project via another library, but essentially our version constraint is
^1.18. This should prevent breaking changes, as it only allows minor updates.However, deployments recently have stopped working, because we have updated to 1.20.0, which it turns out dropped support for MongoDB 3.6 (which Azure Cosmos DB masquerades as):
Dropping support for a MongoDB version should be considered an incompatible API change, so the version of this release should have been 2.0.0. Composer relies on following semver.org guidelines:
Could you consider releasing a version 2.0.0 from the same commit, and adding a new 1.20.1 release which reverts the changes, so that other people using your library doesn't find they are hitting the same issues? The sooner this is done the fewer people it will affect.