Fix for Issue #13652 caused by MongoDB Node.js Driver#13710
Fix for Issue #13652 caused by MongoDB Node.js Driver#13710italojs merged 1 commit intometeor:release-3.3from
Conversation
✅ Deploy Preview for v3-meteor-api-docs canceled.
|
✅ Deploy Preview for v3-migration-docs canceled.
|
|
We had to downgrade the Mongo driver to a specific version because it caused breaking changes in a few apps, including Galaxy, where data was not published properly in an edge case. We should be cautious about including this in 3.3, research and test it beforehand. It would be a pity if existing apps were blocked by a Mongo issue and couldn't benefit from the performance improvements. It might be better to delay it to a future version, with more focus in Mongo. |
|
I’ve reverted the MongoDB upgrade and will postpone it to the next beta, either 3.3.1-beta or 3.4-beta. Upgrading to later versions from mongodb @welkinwong: Feel free to open a new PR with this. After the official Meteor 3.3 we can create a beta for this upgrade. We'll do it otherwise. |
This PR primarily addresses the bug reported in #13652. The issue was caused by the MongoDB Node.js Driver and has been fixed in version v6.16.0.
In Commit 3dac12a, I noticed a temporary version downgrade from 6.10.0 to 6.9.0 due to legacy database connection issues. However, after reviewing the 6.10.0 changelog, the only documented breaking change was the dropped compatibility with MongoDB 3.6. No other critical issues were mentioned in the release notes.
If the issue was solely related to pre-MongoDB 4.x compatibility, I believe we should proceed with the upgrade. According to MongoDB's official support policy (MongoDB Software Lifecycle Schedules), versions below 4.x are already end-of-life (EOL) and no longer supported. Maintaining compatibility with deprecated database versions would introduce unnecessary technical debt and potential security risks.