# 5.7/5.8 release notes > Depth-first rabbithole dossier for 5.7/5.8 release notes; source-anchored research pack. Parent: [MongoDB Java driver 5.x version timeline & 8.0 compatibility](https://llms-explorer.com/tree/mongodb-java-driver-5-x-version-timeline-8-0-compatibility/) · 6 facets · 62 facts · page: https://llms-explorer.com/tree/5-7-5-8-release-notes/ ## Structure and components - 34. 5.8 adds a typed builder API for vector search index definitions. https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 35. 5.8 adds `Aggregates.rerank()` for the `$rerank` stage. The stage needs an Atlas cluster running MongoDB 8.3 or later (JAVA-6052). https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 36. 5.8 adds the `vectorSearch` operator inside `$search`. `SearchOperator.vectorSearch()` does ANN search, `SearchOperator.vectorSearchExact()` does ENN search, and `filter()` applies lexical prefilters (JAVA-6130). https://www.mongod — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#5-8-content` - 1. The 5.7.0 artifact was published to Maven Central on 2026-04-30. https://repo1.maven.org/maven2/org/mongodb/mongodb-driver-sync/ 2. GitHub also dates the r5.7.0 release to 2026-04-30. https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0 3. 5.7.0 was assembled from two betas. r5.7.0-beta0 shipped on 2026-01-16 and r5.7.0-beta1 on 2026-02-26. https://github.com/mongodb/mongo-java-driver/releases?page=2 4. The 5.7.0 GitHub notes list only the changes made after beta1. The docs "What's New in 5.7" section is cumulative and also includes the beta0 and beta1 items. For example, Connec — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/mechanism.md#a-release-timeline-and-packaging` - 44. 5.8.1 contains one fix: reactive streams `MongoClient.getTimeout` always returned `null`. https://github.com/mongodb/mongo-java-driver/releases/tag/r5.8.1 — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#5-8-1-content` - 36. 5.8.1 contains exactly one fix: Reactive Streams `MongoClient.getTimeout` always returned `null` (PR #2011). https://github.com/mongodb/mongo-java-driver/releases/tag/r5.8.1 37. The same `getTimeout` fix shipped in 5.9.0. https://github.com/mongodb/mongo-java-driver/releases — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#5-8-1` ## How it works - **Concept.** The release notes for MongoDB Java driver versions 5.7.0, 5.7.1, 5.8.0 and 5.8.1. The sync, Reactive Streams, Kotlin and Scala drivers ship from one repository, `mongodb/mongo-java-driver`. **In scope:** what the notes say, how each release was built, how the changes work, regressions, edge cases, and where sources disagree. **Out of scope:** other 5.x releases, except where they bound a 5.7/5.8 claim. Also out: server feature internals and sibling frontier items. **Report tags:** [M] mechanism · [H] history · [E] edge-cases · [P] practice. The four reports sit in `~/.g — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md` - 43. **[inference]** Do not deploy 5.7.0 in OSGi runtimes (Felix, Karaf, Eclipse RCP) unless Micrometer is present. Use 5.7.1 or later instead. Basis: claims 25–26. 44. **[inference]** Services that keep many idle change streams on the async or Kotlin drivers get the most out of 5.7, because of the `getMore` connection-release fix (claim 16). If such a service previously raised `maxPoolSize` to work around pool exhaustion, re-check that setting after upgrading. 45. **[inference]** If you use the Scala 3 artifact, the floor is 5.7.1, not 5.7.0 (claim 7). 46. **[inference]** If you use the Reacti — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#operational-implications-inference-unless-cited` - - The 5.9–5.12 release notes, including when the 4.4 minimum actually lands. - The Java driver × MongoDB 8.0/8.3 compatibility matrix. - The Native Reranking and auto-embedding Atlas products. — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/mechanism.md#handoffs-out-of-scope-not-researched` - 6. 5.7 adds Scala 3 support. https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 7. The Scala 3 artifact was not published in 5.7.0. It first became available in 5.7.1. Scala 2.11, 2.12 and 2.13 remain supported. https://www.mongodb.com/docs/languages/scala/scala-driver/current/reference/whats-new/ 8. 5.7.1 includes "Added Scala 3 to publish.sh" (JAVA-6189), which is the packaging fix behind claim 7. https://github.com/mongodb/mongo-java-driver/releases 9. 5.7 adds auto-embedding support to the vector search APIs. https://www.mongodb.com/docs/drivers/java/sync/curre — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#5-7-features` ## Measurements and reference values - 1. 5.7.0-alpha0 was published on 2025-10-22. Only Maven Central shows it; the GitHub releases page lists beta0 and beta1 but no alpha. [E1–2, P1] https://repo1.maven.org/maven2/org/mongodb/mongodb-driver-sync/ 2. 5.7.0-beta0 shipped on 2026-01-16 and beta1 on 2026-02-26. [M3] https://github.com/mongodb/mongo-java-driver/releases?page=2 3. 5.7.0 was published on 2026-04-30 at 15:53. GitHub's r5.7.0 is dated the same day and was authored by `mongodb-dbx-release-bot`. [M1–2, H1, H6] https://repo1.maven.org/maven2/org/mongodb/mongodb-driver-sync/ · https://github.com/mongodb/mongo-java-driver/rele — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md#a-timeline-and-packaging` - 9. The docs site publishes the notes as "What's New in 5.7", "What's New in 5.7.1" and "What's New in 5.8" sections. The page has no separate 5.8.1 section. https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 10. The Reactive Streams driver has its own release-notes page with the same 5.7, 5.7.1 and 5.8 sections. https://www.mongodb.com/docs/languages/java/reactive-streams-driver/current/reference/release-notes/ 11. The Scala driver has a separate "What's New" page with much shorter 5.7, 5.7.1 and 5.8 sections. https://www.mongodb.com/docs/languages/scala/scala-driv — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#where-the-notes-are-published` - | Pass | Focus | New claims | Total claims | New-info rate | |---|---|---|---|---| | 0 | Docs release notes | 30 | 30 | 100% | | 1 | GitHub tags, betas, Maven dates | 11 | 41 | 27% | | 2 | Primary PRs (#1905, #1925, #1813, #1793, #1862, #1962, #1963, #1988) | 9 | 50 | 18% | | 3 | Disconfirmation (the 4.2 drop, 5.8.1, `$rerank` docs) | 3 | 53 | 6% | — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/mechanism.md#saturation` - - https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ - https://www.mongodb.com/docs/languages/java/reactive-streams-driver/current/reference/release-notes/ - https://www.mongodb.com/docs/drivers/kotlin/coroutine/current/reference/release-notes/ - https://www.mongodb.com/docs/languages/scala/scala-driver/current/reference/whats-new/ - https://www.mongodb.com/docs/drivers/compatibility/ - https://www.mongodb.com/docs/drivers/compatibility.md - https://www.mongodb.com/docs/drivers/compatibility/.md - https://www.mongodb.com/docs/drivers/java/sync/current/reference/upg — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md#source-list-only-urls-cited-in-the-four-reports` - - https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ - https://www.mongodb.com/docs/languages/java/reactive-streams-driver/current/reference/release-notes/ - https://www.mongodb.com/docs/languages/scala/scala-driver/current/reference/whats-new/ - https://www.mongodb.com/docs/drivers/compatibility.md - https://www.mongodb.com/docs/drivers/java/sync/current/reference/upgrade/ - https://github.com/mongodb/mongo-java-driver/releases - https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0 - https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.1 - ht — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#sources` - 29. 5.7.1 fixes Javadoc warnings in the Micrometer integration. https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 30. 5.7.1 marks the Micrometer OSGi imports as optional to fix bundle resolution in OSGi runtimes. https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 31. JIRA JAVA-6215 records the underlying bug: "mongodb-driver-core bundle v5.7.0 is unresolved in OSGi". https://jira.mongodb.org/issues/?jql=project%20%3D%20JAVA%20AND%20fixVersion%20%3D%205.8.0 32. The Scala docs say 5.7.1 "Fixes an issue where the Scala 3 artifact was not — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#5-7-1-content` ## Problems, failure modes and limitations - 14. The 5.7 notes say that "an upcoming minor release will drop support for MongoDB Server version 4.2 and raise the minimum supported version to 4.4". They cite the MongoDB Software Lifecycle Schedules. [M11, H14, E25, P28] https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 15. The GitHub r5.7.0 release says: "Support for MongoDB Server 4.2 will be dropped in a future release!" [H15, M12, P29] https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0 16. The same warning first appeared in the 5.6 notes, so it rolls forward from release to release. [M13] syn — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md#b-5-7-the-server-support-notice` - | # | Side A | Side B | What would settle it | |---|---|---|---| | X1 | **Scala 3 in 5.7.0.** Scala docs: "not published in version 5.7.0", available from 5.7.1 [H, P7]. [M17] says 5.7.1 was the first release to publish Scala 3 artifacts. | Maven Central has `mongo-scala-driver_3/5.7.0/`, dated 2026-05-05, five days after release [H]. https://repo1.maven.org/maven2/org/mongodb/scala/mongo-scala-driver_3/ | A publish log, or a statement that the artifact was published by hand | | X2 | **Ticket for the Scala 3 publish fix.** JAVA-6189 "Added Scala 3 to publish.sh" [M6, P8, GitHub r5.7.1] | JAVA- — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md#unresolved-disagreements-side-by-side-not-reconciled` - | Pass | Focus | New claims | Total | Rate | |---|---|---|---|---| | 0 | Docs release notes and GitHub tags | 30 | 30 | 100% | | 1 | Maven timestamps, 5.7.1/5.8.1 tags, compatibility table | 12 | 42 | 29% | | 2 | Scala/Reactive pages, JIRA, testcontainers, upgrade guide | 8 | 50 | 16% | | 3 | Scala 3 Maven check, r5.7.0 PR-level diff | 1 (plus 2 disagreements) | 51 | 2% | | 4 | Re-read for why/limit/exception questions; no new primary source found | 0 | 51 | 0% | — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#saturation-curve` - IN: what the 5.7.x and 5.8.x release notes say, how those releases were assembled (betas, backports, patches), the mechanism behind each headline change, and the invariants and limits the notes state or imply. OUT: other 5.x releases, except where they bound a 5.7/5.8 claim (for example, whether the 5.7 "drop 4.2" warning has landed yet). Also out: the full server-compatibility matrix, and Atlas Vector Search as a product. — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/mechanism.md#scope` - 11. The 5.7 notes warn that "an upcoming minor release will drop support for MongoDB Server version 4.2 and raise the minimum supported version to 4.4". The notes tie this to the MongoDB Software Lifecycle Schedules. https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 12. From claim 11, 5.7 itself still supports MongoDB Server 4.2. The GitHub notes word the same point as "a future minor release will raise the minimum … from 4.2 to 4.4". https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0 13. The same warning already appeared in the 5.6 notes. The warnin — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/mechanism.md#b-5-7-compatibility-notice-invariant-and-limit` - 25. The 5.7.0 `mongodb-driver-core` bundle does not resolve in OSGi containers such as Apache Felix. Its metadata imports `io.micrometer.common` even though Micrometer is an optional dependency (JAVA-6215, affects 5.7.0). https://jira.mongodb.org/browse/JAVA-6215 26. JAVA-6215 is fixed in 5.7.1 and 5.8.0 and was resolved on 2026-05-27. https://jira.mongodb.org/browse/JAVA-6215 27. The 5.8 release notes list the same defect: "Fixes an OSGi bundle resolution failure when Micrometer is not present." https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#5-7-0-regression-osgi` - 38. In OSGi containers such as Felix, 5.7.0's `mongodb-driver-core` bundle does not resolve unless Micrometer is present. The bundle imports Micrometer packages as mandatory, even though the Maven dependency is optional (JAVA-6215). [E5, P25] https://jira.mongodb.org/browse/JAVA-6215 39. Literal error: `Unable to resolve org.mongodb.driver-core [16]: missing requirement osgi.wiring.package; (&(osgi.wiring.package=io.micrometer.common)(version>=1.15.0))`. [E6] JAVA-6215 40. The OSGi fix shipped in 5.7.1 and 5.8.0 (#1982). JAVA-6215 was resolved on 2026-05-27, and 5.7.1 added a bundle-resolution — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md#d-5-7-0-regressions-and-the-5-7-1-fixes` - 5. 5.7.0's `mongodb-driver-core` bundle does not resolve in OSGi containers such as Apache Felix unless Micrometer is present. The bundle declares Micrometer packages as mandatory imports even though the Maven dependency is optional (JAVA-6215). https://jira.mongodb.org/browse/JAVA-6215 6. The literal failure reads: `Unable to resolve org.mongodb.driver-core [16]: missing requirement osgi.wiring.package; (&(osgi.wiring.package=io.micrometer.common)(version>=1.15.0))`. https://jira.mongodb.org/browse/JAVA-6215 7. JAVA-6215 affects only 5.7.0 and is fixed in both 5.7.1 and 5.8.0. The 5.7.1 fix a — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/edge-cases.md#regressions-shipped-in-5-7-0-and-fixed-later` - 18. Reactive-streams 5.7: `commitTransaction()` and `abortTransaction()` now return cold publishers. They "do not run until you subscribe". Code that called them and dropped the returned publisher will no longer commit or abort. https://www.mongodb.com/docs/languages/java/reactive-streams-driver/current/reference/release-notes/ 19. The encryption client (CSFLE/QE key vault path) in 5.7 now uses `writeConcern` majority. Writes to the key vault can therefore take longer or fail on topologies that cannot reach a majority. https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-no — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/edge-cases.md#behaviour-changes-that-can-surprise-an-upgrader` - 14. The 5.7 notes announce that an upcoming minor release will drop MongoDB Server 4.2 and raise the minimum to 4.4, citing the MongoDB Software Lifecycle Schedules. https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 15. The GitHub r5.7.0 release carries the same notice: "Support for MongoDB Server 4.2 will be dropped in a future release!" https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0 16. 5.7 adds Scala 3 support. https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 17. 5.7 adds auto-embedding support as part of the vec — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#5-7-content` - 40. 5.8 adds a typed builder API for vector search index definitions (#1960). https://github.com/mongodb/mongo-java-driver/releases/tag/r5.8.0 41. 5.8 adds `Aggregates.rerank()` for the `$rerank` stage (JAVA-6052, #1963). It has two overloads: `rerank(RerankQuery, String path, int numDocsToRerank, String modelName)` and a multi-path `List` form. https://github.com/mongodb/mongo-java-driver/pull/1963 42. `RerankQuery` accepts either a text shorthand or full BSON, so it can support future query modalities. The PR also shows how to read relevance scores with `$meta: "score"`. https://gith — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/mechanism.md#d-5-8-mechanisms` - 14. In the Reactive Streams driver, 5.7 makes `commitTransaction()` and `abortTransaction()` return cold publishers. They do not run until something subscribes. https://www.mongodb.com/docs/languages/java/reactive-streams-driver/current/reference/release-notes/ 15. **[inference]** Reactive code that called `commitTransaction()` or `abortTransaction()` without subscribing, relying on the earlier eager behaviour, silently stops committing or aborting on 5.7. The Reactive Streams release notes list this as a change, and the upgrade page has no breaking-change entry for 5.7 (see claim 36). https:/ — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#5-7-behaviour-changes-and-fixes` - - **Independence caveat:** four of the five hosts are MongoDB-operated. `docs.spring.io` is the only independent host, and it covers compatibility only, not the change content. - **Disconfirming search:** I looked for 5.7/5.8 regressions. It found JAVA-6215 and the `getTimeout` defect. It also exposed the 4.2-drop contradiction. - **Soft stop, not saturation:** this run is `BUDGET_EXHAUSTED`, not `SATURATED-DEPTH`. Three passes ran, with new-information rates of about 100% → 45% → 25% (≈24 → 44 → 58 raw atomic claims before the final edit to 47). The curve is falling but has not reached the tw — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#quality-gate` - 60. [inf] Reactive code that drops the publisher returned by `commitTransaction()`/`abortTransaction()` silently stops committing or aborting on 5.7. [E18, P15] 61. [inf] Key-vault writes now need a majority, so they can slow down or fail on topologies that cannot reach one. [E19] 62. [inf] Tooling that matches the old thread names with `=` stops matching. Alerts keyed on WARN may start firing when servers leave the cluster. [E16, E23, P21] 63. [inf] Deployments that pin `libmongocrypt` or `crypt_shared` separately must track 1.17.3 (5.7) and 1.18.1 (5.8). [E24] 64. [inf] OSGi users should use — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md#h-failure-modes-for-upgraders-inf-unless-cited` - **Independence caveat.** All the content claims come from MongoDB-run hosts. The only outside checks are the Maven Central timestamps, the testcontainers PR (third-party, content) and Spring docs (compatibility only). No independent blog or news coverage was found for 5.7 or 5.8. — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md#source-list-only-urls-cited-in-the-four-reports` - - Three independent hosts were used: mongodb.com (docs), github.com (release pages and PRs) and repo1.maven.org (publish timestamps). GitHub and Maven Central are separate systems but both are MongoDB-controlled channels. No third-party source, such as a blog or news article, was used for claims. - I looked for disconfirming evidence and found it in D1, D2, D3 and D6. I also checked whether the 5.7 "drop 4.2" warning had landed (claim 14: it has not). - **Gate status: met** for the minimum of three sources and hosts. The caveat is that every source is published by the vendor. — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/mechanism.md#quality-gate` - Met. The report uses 5 independent hosts: mongodb.com docs, github.com (releases and PR), jira.mongodb.org, repo1.maven.org, and the mongodb.com compatibility `.md` export. All are primary or official. Disconfirming evidence was sought and found: claims 2, 8, 15, 26, and the cold-publisher gap. Caveat: fetched GitHub and JIRA pages were read through a summarizing fetcher. Every string quoted above appeared in the fetched output, but claims 21–22 rely on GitHub summaries that were not cross-checked against a second host. — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/edge-cases.md#quality-gate` ## Comparisons and alternatives - - **Reactive cold-publisher change (claim 18).** The reactive docs list it as a 5.7 change. The GitHub notes for 5.7.0-beta0, beta1 and 5.7.0 do not list it. This pass found no PR or JIRA ticket for it. It could be undocumented upstream, or a docs error. Sources: https://www.mongodb.com/docs/languages/java/reactive-streams-driver/current/reference/release-notes/ vs https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0 - **Where the OSGi fix lives (claims 7–8).** GitHub and JIRA put it in 5.7.1 and 5.8.0. The docs credit only 5.8. https://jira.mongodb.org/browse/JAVA-6215 vs https:// — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/edge-cases.md#unresolved-disagreements` - - **In:** what the 5.7 and 5.8 notes say, when each 5.7.x/5.8.x artifact shipped, how the notes differ across publication channels (docs site, GitHub release, JIRA, Maven Central), and what the compatibility table says about 5.7 and 5.8 versus MongoDB 8.x. - **Out:** the 5.6, 5.9, 5.10+ releases (mentioned only as bracketing dates), the wider 5.x timeline, and the features themselves ($rerank, vector search, CSOT, Micrometer). Those are sibling frontier items. — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#scope` - - **D1 — 5.7.1 release date.** The GitHub tag page shows 2026-08-13. The GitHub releases list and Maven Central both show 2026-05-27 (https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.1 vs https://repo1.maven.org/maven2/org/mongodb/mongodb-driver-sync/). The later date is probably a release-page edit, but that is not verified. Use 2026-05-27, the Maven publish date. - **D2 — What the 5.7 "RTT timeout" item changed.** The docs describe it as a production improvement to client-side timeout handling. The PR #1793 description is mostly about test-side RTT handling (https://www.mongodb — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/mechanism.md#unresolved-disagreements` - - **When 4.2 support ends.** The 5.7 notes and the GitHub release say "an upcoming minor release" will drop MongoDB 4.2 (claims 28–29). The compatibility table, however, still marks 4.2 ✓ for drivers 5.8 through 5.11 (claim 38). The upgrade guide has no 4.2-drop section (claim 41), and the Reactive Streams release notes mention no drop after 5.7. Either the drop has not happened yet despite four more minors, or the table is stale. None of the sources I read resolves this. Before a 4.2 deployment relies on any driver newer than 5.7, check the JAVA JIRA fixVersion history. https://www.mongodb.co — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#unresolved-disagreements` - 20. 5.7 adds Scala 3 support (#1904). Scala 2.11, 2.12 and 2.13 remain supported. [M16, P7] r5.7.0 · Scala What's New 21. Auto-embedding (JAVA-5988, #1862) lets `$vectorSearch` take a text query. The server generates the embedding with the model set in the index. [M18] https://github.com/mongodb/mongo-java-driver/pull/1862 22. The auto-embedding API is `VectorSearchQuery.textQuery(String)`. It returns a `TextVectorSearchQuery` with a fluent `.model(String)`, and `Aggregates.vectorSearch()` accepts the typed query. The types are annotated `@Beta(Reason.SERVER)`, so their shape can change with s — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md#c-5-7-how-the-changes-work` - 10. 5.7 "restores the optimized codec path for `RawBsonDocument` encoding". This fixes a performance regression (JAVA-6101, PR #1888, merged 2026-02-24, first shipped in 5.7.0-beta1). https://github.com/mongodb/mongo-java-driver/pull/1888 11. Root cause: PR #1632 switched codec lookup from class-based to `BsonType`-based lookup. After that change, nested `RawBsonDocument` values were encoded through `BsonDocumentCodec` instead of the byte-copy path, because both report `BsonType.DOCUMENT`. https://github.com/mongodb/mongo-java-driver/pull/1888 12. The fix adds an `instanceof RawBsonDocument` c — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/edge-cases.md#fixes-in-5-7-for-earlier-regressions` - - **Was the Scala 3 artifact missing in 5.7.0?** The Scala docs say it "was not published in version 5.7.0" and that it is "available beginning in v5.7.1" (https://www.mongodb.com/docs/languages/scala/scala-driver/current/reference/whats-new/). Maven Central does hold `mongo-scala-driver_3/5.7.0/`, dated 2026-05-05 08:44, five days after the Java 5.7.0 artifacts (https://repo1.maven.org/maven2/org/mongodb/scala/mongo-scala-driver_3/). Most likely it was published by hand after release day, and 5.7.1 fixed the script (JAVA-6191). No source confirms that explanation. - **Docs 5.7 list vs GitHub — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#unresolved-disagreements` - 16. 5.7 adds Scala 3 support (#1904). https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0 17. The Scala 3 artifacts were missing from the 5.7.0 publish script. 5.7.1 fixed this (JAVA-6189), so 5.7.1 is the first release whose Scala 3 artifacts were published. https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.1 18. Auto-embedding (JAVA-5988, #1862) lets `$vectorSearch` accept a text query instead of a precomputed vector. The server generates the embedding with the model configured in the vector search index. https://github.com/mongodb/mongo-java-driver/pull/1862 19. Th — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/mechanism.md#c-5-7-mechanisms` ## Facts and statements - In scope: the MongoDB Java driver 5.7.x and 5.8.x release notes (sync, reactive-streams, Kotlin, Scala share one repo and one release). That covers what they change, what they break, what later patches had to fix, and where the published sources disagree. Out of scope: other 5.x lines as topics in their own right, server release notes, and general 8.0 compatibility. Those are sibling frontier items. 5.6.x and 5.9+ are cited only where they bound a 5.7/5.8 claim. — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/edge-cases.md#scope` - **Concept:** the release notes for MongoDB Java driver minor versions 5.7 (5.7.0, 5.7.1) and 5.8 (5.8.0, 5.8.1). **Parent context:** MongoDB Java driver 5.x version timeline and MongoDB 8.0 compatibility. **Run:** /rabbithole depth pass, 2026-09-24. Verdict: `SATURATED-DEPTH` after 4 passes (see curve at the end). — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md` - - **In scope:** what the 5.7.x and 5.8.x releases of the MongoDB Java driver family changed. That covers the sync, Reactive Streams, Kotlin coroutine and Scala drivers, which share one codebase (`mongodb/mongo-java-driver`). It also covers the patch releases 5.7.1 and 5.8.1, the defects those patches fixed, server and JVM compatibility for these versions, and what an upgrade means in practice. - **Out of scope:** other 5.x minors except where they fix a 5.7/5.8 defect or contradict a 5.7/5.8 notice, server feature internals (only the preconditions the driver notes rely on), and sibling frontie — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#scope` - 42. Typed builder API for vector search index definitions (#1960). [M40, H34] 43. `Aggregates.rerank()` for `$rerank` (JAVA-6052, #1963). It has two overloads: `(RerankQuery, String path, int numDocsToRerank, String modelName)` and a multi-path `List` form. [M41] https://github.com/mongodb/mongo-java-driver/pull/1963 44. `RerankQuery` accepts either text or full BSON, to leave room for future query types. Relevance scores are read with `$meta: "score"`. [M42] PR #1963 45. `$rerank` requirements: Atlas on MongoDB 8.3 or later only (no self-managed or Atlas Local), a Preview feature not — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md#e-5-8-how-the-changes-work` - 54. Drivers 5.2–5.7 are ✓ with MongoDB 4.2 through 8.2 and ⊛ (partial) with 8.3. Drivers 5.8–5.11 are ✓ with 4.2 through 8.3, so 5.8 is the first fully 8.3-compatible line. [H45–46, E27, P38] compatibility page 55. For MongoDB 8.0, 5.7 and 5.8 behave the same: every driver from 5.2 onward is fully compatible. [H47, P39] 56. Drivers 4.11–5.11 support Java 8, 11, 17 and 21, so neither release changed the JDK baseline. [H49, P40] 57. The compatibility page says every 5.x version, 5.7 and 5.8 included, "is not compatible with virtual threads". [E29] https://www.mongodb.com/docs/drivers/compatibili — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md#g-compatibility-boundaries` - - The release that actually drops MongoDB 4.2, including whether 5.12 exists (X8, X9) - The 5.9 release notes (QE prefix/suffix/substring GA, `Text`→`String` rename) - Client backpressure, from the 5.8 prep work through to the release that ships it - `$rerank` / MongoDB 8.3 feature support across drivers; the Native Reranking and auto-embedding Atlas products - The Java driver × 8.0/8.3 compatibility matrix as a topic in its own right — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md#handoffs-to-concept-family-explorer-not-researched-here` - 1. 5.7.0 shipped on 2026-04-30, after a 5.7.0-alpha0 (2025-10-22), beta0 (2026-01-16) and beta1 (2026-02-26). https://repo1.maven.org/maven2/org/mongodb/mongodb-driver-sync/ 2. The GitHub releases page lists beta0 and beta1 but no alpha0. Maven Central is the only source that shows the alpha. https://github.com/mongodb/mongo-java-driver/releases?page=2 3. 5.7.1 shipped on 2026-05-27, 5.8.0 on 2026-05-28 and 5.8.1 on 2026-07-16. https://github.com/mongodb/mongo-java-driver/releases 4. Maven Central shows 5.8.1 (2026-07-16) arriving after 5.9.0 (2026-07-07). So 5.8.1 is a back-patch to an older — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/edge-cases.md#release-timeline-boundaries` - 25. 5.7 warns that "an upcoming minor release will drop support for MongoDB Server version 4.2 and raise the minimum supported version to 4.4". https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 26. Disconfirming: that drop did not land in 5.8. The compatibility table still marks 5.8–5.11 fully compatible (✓) with MongoDB 4.2. https://www.mongodb.com/docs/drivers/compatibility/.md 27. The compatibility table marks 5.2–5.7 as only partially compatible (⊛) with MongoDB 8.3. 5.8 is the first line marked ✓ for 8.3. https://www.mongodb.com/docs/drivers/compatibility/.md — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/edge-cases.md#server-version-boundaries` - 1. The `mongodb-driver-sync` 5.7.0 artifact was published to Maven Central on 2026-04-30 15:53. https://repo1.maven.org/maven2/org/mongodb/mongodb-driver-sync/ 2. The 5.7.1 artifact was published on 2026-05-27 11:13. https://repo1.maven.org/maven2/org/mongodb/mongodb-driver-sync/ 3. The 5.8.0 artifact was published on 2026-05-28 17:07, about 30 hours after 5.7.1. https://repo1.maven.org/maven2/org/mongodb/mongodb-driver-sync/ 4. The 5.8.1 artifact was published on 2026-07-16 17:31. 5.9.0 had already shipped on 2026-07-07, so 5.8.1 is a backport patch published after the next minor. https://rep — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#release-timeline` - 45. The compatibility table marks Java driver 5.8 to 5.11 as fully compatible (✓) with MongoDB 8.3, 8.1–8.2, 8.0, 7.0, 6.0, 5.0, 4.4 and 4.2. https://www.mongodb.com/docs/drivers/compatibility.md 46. The same table marks 5.2 to 5.7 as ✓ for 8.0 and 8.1–8.2 but only partially compatible (⊛) with MongoDB 8.3. On MongoDB 8.3, 5.8 is therefore the first fully compatible version. https://www.mongodb.com/docs/drivers/compatibility.md 47. The table recommends 5.2 or later for full MongoDB 8.0 support, so both 5.7 and 5.8 are fully 8.0-compatible. https://www.mongodb.com/docs/drivers/compatibility.md — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#compatibility-and-upgrade-impact` - - The release that actually drops MongoDB Server 4.2 (5.12 or later?). - The 5.9 release notes (QE prefix/suffix/substring GA, `Text`→`String` rename). - `$rerank` / MongoDB 8.3 feature support across drivers. - Client backpressure (preliminary refactor in 5.8, shipped in 5.12.0). — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#handoffs-siblings-surfaced-not-researched` - 1. 5.7.0 reached Maven Central on 2026-04-30. Its pre-releases were 5.7.0-alpha0 (2025-10-22), beta0 (2026-01-16) and beta1 (2026-02-26). https://repo1.maven.org/maven2/org/mongodb/mongodb-driver-sync/ 2. The GitHub release for r5.7.0 is dated April 30, 2026, which matches Maven Central. https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0 3. 5.7.1 shipped 2026-05-27, and 5.8.0 shipped the next day, 2026-05-28. https://repo1.maven.org/maven2/org/mongodb/mongodb-driver-sync/ 4. 5.8.1 shipped 2026-07-16, nine days after 5.9.0 (2026-07-07). The 5.8 line therefore received a backported — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#timeline-artifact-level` - 28. The 5.7 notes say: "An upcoming minor release will drop support for MongoDB Server version 4.2 and raise the minimum supported version to 4.4." https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 29. The r5.7.0 GitHub release repeats this notice: a future minor will raise the minimum server version from 4.2 to 4.4. https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0 — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#5-7-deprecation-notice` - 30. 5.8 adds a typed builder API for vector search index definitions, including `VectorSearchIndexDefinition.storedSource()`. https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 31. 5.8 adds `VectorSearchOptions.returnStoredSource()`, which returns stored-source fields from `$vectorSearch`. https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ 32. 5.8 adds `SearchOperator.vectorSearch()` (approximate nearest neighbour, ANN) and `SearchOperator.vectorSearchExact()` (exact nearest neighbour, ENN) inside `$search`. The `filter()` method on the — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#5-8-features` - 38. Server compatibility table: drivers 5.2–5.7 are ✓ (fully compatible) for MongoDB 4.2 through 8.2, including 8.0, and ⊛ (partial) for 8.3. Drivers 5.8–5.11 are ✓ for 4.2 through 8.3. https://www.mongodb.com/docs/drivers/compatibility/ 39. So for MongoDB 8.0, moving from 5.7 to 5.8 changes nothing. Both are fully compatible, as is every driver from 5.2 onward. Only 8.3 features such as `$rerank` need 5.8. https://www.mongodb.com/docs/drivers/compatibility/ 40. JVM compatibility: drivers 4.11–5.11, which includes 5.7 and 5.8, are listed as fully compatible with Java 8, 11, 17 and 21. https:// — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#compatibility-the-parent-concern` - 53. 5.8.1 has one fix (#2011): Reactive Streams `MongoClient.getTimeout` always returned `null`. The same fix also shipped in 5.9.0. [M9, H44, P36–37] https://github.com/mongodb/mongo-java-driver/releases/tag/r5.8.1 — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md#f-5-8-1` - MongoDB operates three of these hosts, so they share an author. Maven Central timestamps and the testcontainers PR are the non-MongoDB checks. I searched for a disconfirming source on purpose, and the Maven Scala 3 listing contradicts the docs (see the first disagreement). No independent editorial coverage, such as a blog post or news article, was found for 5.7 or 5.8. — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#quality-gate` - Also open: which release first shipped the PR #1632 `RawBsonDocument` regression [E], and whether the sync driver gets the `getMore` fix. The sources state it only for the async and Kotlin drivers [M28, P17]. — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/rabbithole-synthesis.md#unresolved-disagreements-side-by-side-not-reconciled` - - https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ - https://www.mongodb.com/docs/languages/java/reactive-streams-driver/current/reference/release-notes/ - https://www.mongodb.com/docs/drivers/compatibility/.md - https://github.com/mongodb/mongo-java-driver/releases - https://github.com/mongodb/mongo-java-driver/releases?page=2 - https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0 - https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0-beta0 - https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0-beta1 - https://github.com/mongo — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/edge-cases.md#sources` - **Met.** The report uses 5 independent hosts: - mongodb.com docs (sync, reactive, Scala and compatibility pages) - github.com/mongodb (release tags) - repo1.maven.org (Maven Central publish timestamps) - jira.mongodb.org (fixVersion issue lists) - github.com/testcontainers (a third-party Dependabot PR) — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/history.md#quality-gate` - - https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ - https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.0 - https://github.com/mongodb/mongo-java-driver/releases/tag/r5.7.1 - https://github.com/mongodb/mongo-java-driver/releases/tag/r5.8.0 - https://github.com/mongodb/mongo-java-driver/releases/tag/r5.8.1 - https://github.com/mongodb/mongo-java-driver/releases - https://github.com/mongodb/mongo-java-driver/releases?page=2 - https://github.com/mongodb/mongo-java-driver/pull/1793 - https://github.com/mongodb/mongo-java-driver/pull/1813 - https://github. — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/mechanism.md#sources` - **Met.** I used five distinct hosts: `mongodb.com` (docs), `github.com` (release tags), `repo1.maven.org` (artifact dates), `jira.mongodb.org` (defect record) and `docs.spring.io` (a third-party consumer matrix). — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#quality-gate` - - https://www.mongodb.com/docs/drivers/java/sync/current/reference/release-notes/ - https://www.mongodb.com/docs/languages/java/reactive-streams-driver/current/reference/release-notes/ - https://www.mongodb.com/docs/drivers/kotlin/coroutine/current/reference/release-notes/ - https://www.mongodb.com/docs/languages/scala/scala-driver/current/reference/whats-new/ - https://www.mongodb.com/docs/drivers/compatibility/ - https://www.mongodb.com/docs/drivers/java/sync/current/reference/upgrade/ - https://www.mongodb.com/docs/vector-search/query/aggregation-stages/rerank/ - https://github.com/mongodb/ — source: `~/.global-ai-hub/research-runs/frontier-2026-09-24/5-7-5-8-release-notes/reports/practice.md#sources` ## Related concepts - release — is a part of 5.7/5.8 release notes - 5.7 — is a part of 5.7/5.8 release notes - 5.8 — is a part of 5.7/5.8 release notes - notes — is a part of 5.7/5.8 release notes