DOCSP-50020 Remove EOL mentions (#133) (#135) (#136)

* DOCSP-50020 Remove EOL mentions

* MM review

* remove froom compat table

(cherry picked from commit cebb98b)
(cherry picked from commit 6347035)

Co-authored-by: lindseymoore <[email protected]>

Author: github-actions[bot]

source/aggregation.txt

@@ -197,11 +197,10 @@ plan:
 Run an Atlas Full-Text Search
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. tip:: Only Available on Atlas for MongoDB v4.2 and later
+.. tip:: Only Available for 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/>`.
 
 To specify a full-text search of one or more fields, you can create
 a ``$search`` pipeline stage. The {+driver-short+} provides the

source/connect/stable-api.txt

@@ -17,10 +17,6 @@ Stable API
 .. meta::
    :keywords: compatible, backwards, upgrade
 
-.. note::
-
-   The Stable API feature requires {+mdb-server+} 5.0 or later.
-
 Overview
 --------
 
@@ -106,7 +102,7 @@ Unrecognized field 'apiVersion' on server
 
 The {+driver-short+} raises this exception if you specify an API version and connect to a
 MongoDB server that doesn't support the {+stable-api+}. Ensure you're connecting to a
-deployment running {+mdb-server+} v5.0 or later.
+deployment running {+mdb-server+} v6.0 or later.
 
 Provided apiStrict:true, but the command count is not in API Version
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

source/databases-collections/time-series.txt

@@ -51,11 +51,6 @@ series data:
 Create a Time Series Collection
 -------------------------------
 
-.. important:: Server Version for Time Series Collections
-
-   To create and interact with time series collections, you must be
-   connected to a deployment running {+mdb-server+} 5.0 or later.
-
 You can create a time series collection to store time series data.  
 To create a time series collection, pass the following parameters to the 
 ``createCollection()`` method:

source/includes/mongodb-compatibility-table-scala.rst

@@ -8,52 +8,27 @@
      - MongoDB 7.0
      - MongoDB 6.1
      - MongoDB 6.0
-     - MongoDB 5.0
-     - MongoDB 4.4
-     - MongoDB 4.2
-     - MongoDB 4.0
-     - MongoDB 3.6
 
    * - 5.2 to 5.3
      - ✓
      - ✓
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - 
 
    * - 4.10 to 5.1
      - ⊛
      - ✓
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
 
    * - 4.8 to 4.9
      - ⊛
      - ⊛
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
 
    * - 4.7
      - ⊛
      - ⊛
      - ⊛
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓

source/security/auth.txt

@@ -31,10 +31,8 @@ mechanisms.
 Default Authentication Mechanism
 --------------------------------
 
-In MongoDB 3.0, MongoDB changed the default authentication mechanism
-from ``MONGODB-CR`` to ``SCRAM-SHA-1``. In MongoDB 4.0, support for
-the deprecated ``MONGODB-CR`` mechanism was removed and ``SCRAM-SHA-256`` support was
-added.
+The default authentication mechanism for MongoDB 6.0 and later is
+``SCRAM-SHA-256``.
 
 To create a credential that authenticates by using the default
 authentication mechanism, regardless of server version, create a
@@ -57,12 +55,6 @@ authentication mechanism:
    :copyable:
    :dedent:
 
-For challenge and response mechanisms, we recommend using the default
-authentication mechanism. This approach simplifies upgrading from MongoDB 2.6 to MongoDB
-3.0, even after upgrading the authentication schema. For MongoDB 4.0 users, we also recommend
-the default authentication mechanism because it checks the mechanisms and uses the correct
-hashing algorithm.
-
 SCRAM-Based Mechanisms
 ----------------------
 
@@ -73,15 +65,11 @@ based on the `IETF RFC 5802
 best practices for implementation of challenge-response mechanisms for authenticating
 users with passwords.
 
-MongoDB 3.0 introduced support for ``SCRAM-SHA-1``, which uses the
-``SHA-1`` hashing function. MongoDB 4.0 introduced support for ``SCRAM-SHA-256`` which
-uses the ``SHA-256`` hashing function.
-
 SCRAM-SHA-256
 ~~~~~~~~~~~~~
 
-Using this mechanism requires MongoDB 4.0 and
-``featureCompatibilityVersion`` to be set to 4.0.
+Using this mechanism requires ``featureCompatibilityVersion`` to be set to 4.0 
+or a later version.
 
 To explicitly create a credential of type ``SCRAM-SHA-256``, use
 the ``createScramSha256Credential()`` method:
@@ -103,29 +91,6 @@ Or, you can use a connection string that explicitly specifies
    :copyable:
    :dedent:
 
-SCRAM-SHA-1
-~~~~~~~~~~~
-
-To explicitly create a credential of type ``SCRAM-SHA-1``, use the
-``createScramSha1Credential()`` method:
-
-.. literalinclude:: /includes/security/auth.scala
-   :start-after: start-scram-sha-1
-   :end-before: end-scram-sha-1
-   :language: scala
-   :copyable:
-   :dedent:
-
-Or, you can use a connection string that explicitly specifies
-``authMechanism=SCRAM-SHA-1``:
-
-.. literalinclude:: /includes/security/auth.scala
-   :start-after: start-scram-sha-1-connection-string
-   :end-before: end-scram-sha-1-connection-string
-   :language: scala
-   :copyable:
-   :dedent:
-
 x.509
 -----