DOCSP-50017 Remove EOL versions (#220) (#221)

github-actions[bot] · lindseymoore · lindseymoore · commit 6a860497334c · 2025-05-22T22:39:16.000-04:00
* DOCSP-50017 Remove EOL versions * auth * auth suggestion NR * NR comments * get rid of font on headings (cherry picked from commit 94fd075) Co-authored-by: lindseymoore <71525840+lindseymoore@users.noreply.github.com> (cherry picked from commit 7046a65)
diff --git a/source/fundamentals/auth.txt b/source/fundamentals/auth.txt
@@ -23,10 +23,7 @@ confirm identity and establish trust to ensure security.
 The mechanisms that you can use with the latest version of MongoDB Community
 Edition are as follows:
 
-* :ref:`Default <default-auth-mechanism>`
 * :ref:`SCRAM-SHA-256 <scram-sha-256-auth-mechanism>`
-* :ref:`SCRAM-SHA-1 <scram-sha-1-auth-mechanism>`
-* :ref:`MONGODB-CR <mongodb-cr-auth-mechanism>`
 * :ref:`MONGODB-AWS <mongodb-aws-auth-mechanism>`
 * :ref:`X.509 <x509-auth-mechanism>`
 
@@ -45,38 +42,31 @@ Mechanisms
 ----------
 
 .. _default-auth-mechanism:
+.. _scram-sha-256-auth-mechanism:
 
-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``
+SCRAM-SHA-256
+~~~~~~~~~~~~~
 
-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.
+``SCRAM-SHA-256`` is a salted challenge-response authentication mechanism
+(SCRAM) that uses your username and password, encrypted with the ``SHA-256``
+algorithm, to authenticate your user. This is the default authentication
+mechanism.
 
 The following code snippets show how to specify the authentication mechanism,
 using the following placeholders:
 
-* ``db_username`` - your MongoDB database username
-* ``db_password`` - your MongoDB database user's password
-* ``hostname`` - network address of your MongoDB server, accessible by your client
-* ``port`` - port number of your MongoDB server
+* ``db_username`` - your MongoDB database username.
+* ``db_password`` - your MongoDB database user's password.
+* ``hostname`` - network address of your MongoDB server, accessible by your client.
+* ``port`` - port number of your MongoDB server.
 * ``authenticationDb`` - MongoDB database that contains your user's
   authentication data. If you omit this parameter, the driver uses the
   default value ``admin``.
 
 Select the :guilabel:`Connection String` or the :guilabel:`MongoCredential`
-tab below for instructions and sample code for specifying this authentication
+tab below for instructions and sample code to specify this default authentication
 mechanism:
 
-.. _mongo-client-setting-with-mongo-credential-example:
-
 .. tabs::
 
    .. tab::
@@ -99,38 +89,10 @@ mechanism:
       .. literalinclude:: /examples/generated/AuthTest.snippet.default-mongo-cred.kt
          :language: kotlin
 
-For more information on the challenge-response (CR) and salted
-challenge-response authentication mechanisms (SCRAM) that MongoDB supports,
-see the :manual:`SCRAM </core/security-scram/>` section of the Server manual.
-
-.. _scram-sha-256-auth-mechanism:
-
-``SCRAM-SHA-256``
-~~~~~~~~~~~~~~~~~
-
-.. note::
-
-   ``SCRAM-SHA-256`` is the default authentication method for MongoDB starting
-   in MongoDB 4.0.
-
-``SCRAM-SHA-256`` is a salted challenge-response authentication mechanism
-(SCRAM) that uses your username and password, encrypted with the ``SHA-256``
-algorithm, to authenticate your user.
-
-The following code snippets show how to specify the authentication mechanism,
-using the following placeholders:
-
-* ``db_username`` - your MongoDB database username.
-* ``db_password`` - your MongoDB database user's password.
-* ``hostname`` - network address of your MongoDB server, accessible by your client.
-* ``port`` - port number of your MongoDB server.
-* ``authenticationDb`` - MongoDB database that contains your user's
-  authentication data. If you omit this parameter, the driver uses the
-  default value ``admin``.
-
-Select the :guilabel:`Connection String` or the :guilabel:`MongoCredential`
-tab below for instructions and sample code for specifying this authentication
-mechanism:
+You can also explicitly specify the ``SCRAM-SHA-256`` authentication mechanism,
+as shown in the following code snippets. Select the :guilabel:`Connection String` 
+or the :guilabel:`MongoCredential` tab below for instructions and sample code for 
+specifying this authentication mechanism:
 
 .. tabs::
 
@@ -156,76 +118,10 @@ mechanism:
       .. literalinclude:: /examples/generated/AuthTest.snippet.scram-sha-256-cred.kt
          :language: kotlin
 
-.. _scram-sha-1-auth-mechanism:
-
-``SCRAM-SHA-1``
-~~~~~~~~~~~~~~~
-
-.. note::
-   ``SCRAM-SHA-1`` is the default authentication method for MongoDB versions
-   3.0, 3.2, 3.4, and 3.6.
-
-``SCRAM-SHA-1`` is a salted challenge-response mechanism (SCRAM) that uses your
-username and password, encrypted with the ``SHA-1`` algorithm, to authenticate
-your user.
-
-The following code snippets show how to specify the authentication mechanism,
-using the following placeholders:
-
-* ``db_username`` - your MongoDB database username.
-* ``db_password`` - your MongoDB database user's password.
-* ``hostname`` - network address of your MongoDB server, accessible by your client.
-* ``port`` - port number of your MongoDB server.
-* ``authenticationDb`` - MongoDB database that contains your user's
-  authentication data. If you omit this parameter, the driver uses the
-  default value ``admin``.
-
-Select the :guilabel:`Connection String` or the :guilabel:`MongoCredential`
-tab below for instructions and sample code for specifying this authentication
-mechanism:
-
-.. tabs::
-
-   .. tab::
-      :tabid: Connection String
-
-      To specify the ``SCRAM-SHA-1`` authentication mechanism using a
-      connection string, assign the ``authMechanism`` parameter the value
-      ``SCRAM-SHA-1`` in your connection string. Your code to instantiate
-      a ``MongoClient`` should resemble the following:
-
-      .. literalinclude:: /examples/generated/AuthTest.snippet.scram-sha-1-string.kt
-         :language: kotlin
-
-   .. tab::
-      :tabid: MongoCredential
-
-      To specify the default authentication mechanism using the
-      ``MongoCredential`` class, use the
-      `createScramSha1Credential() <{+api+}/apidocs/mongodb-driver-core/com/mongodb/MongoCredential.html#createScramSha1Credential(java.lang.String,java.lang.String,char[])>`__
-      method. Your code to instantiate a ``MongoClient`` should resemble the following:
-
-      .. 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``
-~~~~~~~~~~~~~~~
+MONGODB-AWS
+~~~~~~~~~~~
 
 .. note::
 
@@ -448,8 +344,8 @@ method:
    
 .. _x509-auth-mechanism:
 
-``X.509``
-~~~~~~~~~
+X.509
+~~~~~
 
 The ``X.509`` authentication mechanism uses
 :wikipedia:`TLS <Transport_Layer_Security>` with X.509 certificates to
diff --git a/source/fundamentals/builders/aggregates.txt b/source/fundamentals/builders/aggregates.txt
@@ -864,11 +864,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.
 
@@ -889,13 +888,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
@@ -229,12 +229,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
@@ -230,7 +230,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
@@ -97,8 +97,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
@@ -434,9 +434,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
 ~~~~~~~~~~~~~~
@@ -569,7 +568,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
@@ -11,13 +11,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
@@ -50,10 +50,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() <{+api+}/apidocs/mongodb-driver-kotlin-coroutine/mongodb-driver-kotlin-coroutine/com.mongodb.kotlin.client.coroutine/-mongo-database/run-command.html>`__ method.
 
@@ -90,8 +86,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
diff --git a/source/usage-examples/bulkWrite.txt b/source/usage-examples/bulkWrite.txt
diff --git a/source/usage-examples/count.txt b/source/usage-examples/count.txt
