mongodb · lindseymoore · May 23, 2025 · May 22, 2025 · May 22, 2025 · May 22, 2025
diff --git a/source/fundamentals/auth.txt b/source/fundamentals/auth.txt
@@ -52,16 +52,7 @@ Mechanisms
 Default
 ~~~~~~~
 
-The default authentication mechanism setting uses one of the following
-authentication mechanisms depending on what your MongoDB server supports:
-
-#. ``SCRAM-SHA-256``
-#. ``SCRAM-SHA-1``
-#. ``MONGODB-CR``
-
-Server versions 3.6 and earlier use ``MONGODB-CR`` as the default
-mechanism. Newer versions of the server use one of the mechanisms for
-which they advertise support.
+The default authentication mechanism is ``SCRAM-SHA-256``.
 
 The following code snippets show how to specify the authentication mechanism,
 using the following placeholders:
@@ -211,20 +202,6 @@ mechanism:
       .. literalinclude:: /examples/generated/AuthTest.snippet.scram-sha-1-cred.kt
          :language: kotlin
 
-.. _mongodb-cr-auth-mechanism:
-
-``MONGODB-CR``
-~~~~~~~~~~~~~~
-
-``MONGODB-CR`` is a challenge-response authentication mechanism that uses your
-username and password to authenticate your user. This authentication
-mechanism was deprecated starting in MongoDB 3.6 and is no longer
-supported as of MongoDB 4.0.
-
-You cannot specify this method explicitly; refer to the fallback provided
-by the :ref:`default authentication mechanism <default-auth-mechanism>` to
-connect using ``MONGODB-CR``.
-
 .. _mongodb-aws-auth-mechanism:
 
 ``MONGODB-AWS``

diff --git a/source/fundamentals/builders/aggregates.txt b/source/fundamentals/builders/aggregates.txt
@@ -870,11 +870,10 @@ Atlas Full-Text Search
 Use the ``search()`` method to create a :manual:`$search </reference/operator/aggregation/search/>`
 pipeline stage that specifies a full-text search of one or more fields.
 
-.. tip:: Only Available on Atlas for MongoDB v4.2 and later
+.. tip:: Only Available on Collections with an Atlas Search Index
 
-   This aggregation pipeline operator is only available for collections hosted
-   on :atlas:`MongoDB Atlas </>` clusters running v4.2 or later that are
-   covered by an :atlas:`Atlas search index </reference/atlas-search/index-definitions/>`.
+   This aggregation pipeline operator is only available for collections
+   with an :atlas:`Atlas search index </reference/atlas-search/index-definitions/>`.
    Learn more about the required setup and the functionality of this operator
    from the :ref:`Atlas Search <fts-top-ref>` documentation.
 
@@ -920,13 +919,6 @@ Use the ``searchMeta()`` method to create a
 pipeline stage which returns only the metadata part of the results from
 Atlas full-text search queries.
 
-.. tip:: Only Available on Atlas for MongoDB v4.4.11 and later
-
-   This aggregation pipeline operator is only available
-   on :atlas:`MongoDB Atlas </>` clusters running v4.4.11 and later. For a
-   detailed list of version availability, see the MongoDB Atlas documentation
-   on :atlas:`$searchMeta </atlas-search/query-syntax/#-searchmeta>`.
-
 The following example shows the ``count`` metadata for an Atlas search
 aggregation stage:
 

diff --git a/source/fundamentals/builders/projections.txt b/source/fundamentals/builders/projections.txt
@@ -230,12 +230,6 @@ When you've specified matching criteria in the **query** portion of your operati
 variant to specify a :manual:`positional projection </reference/operator/projection/positional/#sorts-and-the-positional-operator>` to include
 the first element of an array. Only documents that match the query filter will be retrieved.
 
-.. important::
-
-   In MongoDB version 4.4 and earlier, the specified array field must appear in the query filter. Beginning in MongoDB 4.4,
-   you can use a positional project on an array field that does not appear in the query filter.
-
-
 The following example projects the first element of the ``temperatures`` array:
 
 .. io-code-block::

diff --git a/source/fundamentals/connection/network-compression.txt b/source/fundamentals/connection/network-compression.txt
@@ -17,9 +17,9 @@ and your application.
 
 The driver supports the following algorithms:
 
-1. `Snappy <https://google.github.io/snappy/>`__: available in MongoDB 3.4 and later.
-#. `Zlib <https://zlib.net/>`__: available in MongoDB 3.6 and later.
-#. `Zstandard <https://github.com/facebook/zstd/>`__: available in MongoDB 4.2 and later.
+1. `Snappy <https://google.github.io/snappy/>`__
+#. `Zlib <https://zlib.net/>`__
+#. `Zstandard <https://github.com/facebook/zstd/>`__
 
 The driver tests against the following versions of these libraries:
 

diff --git a/source/fundamentals/crud/read-operations/sort.txt b/source/fundamentals/crud/read-operations/sort.txt
@@ -320,9 +320,9 @@ The data is modeled with the following Kotlin data class:
       OrderScore(id=5, description=one large vanilla and chocolate cake, score=0.6)
       OrderScore(id=2, description=two medium vanilla birthday cakes, score=0.6)
 
-.. note:: Text Search Behavior in MongoDB 4.4 or Later
+.. note:: Text Search Behavior in MongoDB 6.0 or Later
 
-   The structure of text search has changed for MongoDB 4.4 or later. You no
+   The structure of text search has changed for MongoDB 6.0 or later. You no
    longer need to project ``Projections.metaTextScore()`` into your
    ``FindFlow`` instance in order to sort on the text score. In addition,
    the field name you specify in a ``$meta`` text score aggregation operation

diff --git a/source/fundamentals/enterprise-auth.txt b/source/fundamentals/enterprise-auth.txt
@@ -229,7 +229,7 @@ to improve performance.
 LDAP (PLAIN)
 ~~~~~~~~~~~~
 
-*Available in MongoDB Enterprise Edition 3.4 and later.*
+*Available in MongoDB Enterprise Edition.*
 
 You can authenticate to a Lightweight Directory Access Protocol (LDAP)
 server using your directory server username and password.

diff --git a/source/fundamentals/indexes.txt b/source/fundamentals/indexes.txt
@@ -98,8 +98,8 @@ your application uses indexes:
   operation updates an indexed field, MongoDB updates the related index.
 
 Since MongoDB supports dynamic schemas, applications can query against fields whose names cannot be known in advance or
-are arbitrary. MongoDB 4.2 introduced :manual:`wildcard indexes </core/index-wildcard/>` to help support these queries.
-Wildcard indexes are not designed to replace workload-based index planning.
+are arbitrary with :manual:`wildcard indexes </core/index-wildcard/>`. Wildcard indexes are 
+not designed to replace workload-based index planning.
 
 For more information on designing your data model and choosing indexes appropriate for your application, see the MongoDB
 server documentation on :manual:`Indexing Strategies </applications/indexes>` and
@@ -453,9 +453,8 @@ created in the preceding code snippet:
    :language: kotlin
 
 MongoDB also supports ``2d`` indexes for calculating distances on a
-Euclidean plane and for working with the "legacy coordinate pairs"
-syntax used in MongoDB 2.2 and earlier. To learn more, see
-:manual:`Geospatial Queries </geospatial-queries>` in the Server manual.
+Euclidean plane. To learn more, see :manual:`Geospatial Queries </geospatial-queries>` 
+in the Server manual.
 
 Unique Indexes
 ~~~~~~~~~~~~~~
@@ -588,7 +587,7 @@ The following snippet removes the "title_text" index from the collection:
 Remove an Index Using a Wildcard Character
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Starting with MongoDB 4.2, you can drop all indexes by calling the
+You can drop all indexes by calling the
 ``dropIndexes()`` method on your collection:
 
 .. literalinclude:: /examples/generated/IndexesTest.snippet.drop-all-indexes.kt

diff --git a/source/fundamentals/stable-api.txt b/source/fundamentals/stable-api.txt
@@ -14,13 +14,6 @@
    :depth: 1
    :class: singlecol
 
-.. note::
-
-   The {+stable-api+} feature requires MongoDB Server 5.0 or later.
-
-   You should only use the {+stable-api+} feature if all the MongoDB
-   servers you are connecting to support this feature.
-
 Overview
 --------
 

diff --git a/source/fundamentals/time-series.txt b/source/fundamentals/time-series.txt
@@ -53,10 +53,6 @@ method:
 .. literalinclude:: /examples/generated/TimeSeriesTest.snippet.create-time-series-collection.kt
    :language: kotlin
 
-.. important::
-
-   Versions prior to MongoDB 5.0 cannot create a time series collection.
-
 To check if you successfully created the collection, send the
 ``"listCollections"`` command to the `runCommand() <{+driver-api+}/-mongo-database/run-command.html>`__ method.
 
@@ -93,8 +89,7 @@ and :ref:`aggregating data <kotlin-aggregation>`.
 
 .. note:: Window Functions
 
-   MongoDB version 5.0 introduces window functions into the aggregation
-   pipeline. You can use window functions to perform operations on a
+   You can use window functions to perform operations on a
    contiguous span of time series data.
 
 For more information, see our

diff --git a/source/includes/mongodb-compatibility-table-kotlin.rst b/source/includes/mongodb-compatibility-table-kotlin.rst
@@ -7,38 +7,18 @@
      - MongoDB 8.0
      - MongoDB 7.0
      - MongoDB 6.0
-     - MongoDB 5.0
-     - MongoDB 4.4
-     - MongoDB 4.2
-     - MongoDB 4.0
-     - MongoDB 3.6
 
    * - 5.5
      - ✓
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     -
-     -
 
    * - 5.2 to 5.4
      - ✓
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     -
 
    * - 4.10 to 5.1
      - ⊛
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
diff --git a/source/usage-examples/bulkWrite.txt b/source/usage-examples/bulkWrite.txt
@@ -34,9 +34,8 @@ The ``bulkWrite()`` method accepts the following parameters:
 
 .. note::
 
-   Retryable writes run on MongoDB server versions 3.6 or later in bulk
-   write operations unless they include one or more instances of 
-   ``UpdateManyModel`` or ``DeleteManyModel``.
+   Retryable writes run in bulk write operations unless they include one or 
+   more instances of ``UpdateManyModel`` or ``DeleteManyModel``.
 
 .. tip::
 

diff --git a/source/usage-examples/count.txt b/source/usage-examples/count.txt
@@ -36,15 +36,6 @@ When you call the ``countDocuments()`` method, you can optionally pass a
 **query filter** parameter. You cannot pass any parameters when you call
 ``estimatedDocumentCount()``.
 
-.. important:: Stable API V1 and MongoDB Server Issue
-
-   If you are using the Stable API ``V1`` with the "strict" option and a 
-   MongoDB server version between 5.0.0 and 5.0.8 inclusive, method calls to
-   ``estimatedDocumentCount()`` may error due to a server bug. 
-
-   Upgrade to MongoDB server 5.0.9 or set the Stable API "strict" option to 
-   ``false`` to avoid this issue.
-
 You can also pass an optional parameter to either of these methods to
 specify the behavior of the call: