Skip to content

DOCSP-50028 Remove EOL mentions #153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 23, 2025
Merged

DOCSP-50028 Remove EOL mentions #153

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
035e593
DOCSP-50028 Remove EOL mentions
lindseymoore May 22, 2025
10795c6
compat table
lindseymoore May 22, 2025
0b4ce17
NR review
lindseymoore May 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions source/aggregation.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -174,11 +174,10 @@ from the preceding :ref:`ruby-aggregation-example`:
Run an Atlas Full-Text Search
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.. note:: Only Available on Atlas for MongoDB v4.2 and later
.. note:: 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.
Expand Down
4 changes: 2 additions & 2 deletions source/connect/connection-options.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,8 +179,8 @@ Authentication
- | The mechanism that the {+driver-short+} uses to authenticate the application.
|
| **Data Type**: ``Symbol``
| **Default**: ``nil`` if user credentials are not supplied.
| ``:scram256`` when connecting to MongoDB v4.0 or later.
| **Default**: ``:scram256``
| ``nil`` if user credentials are not supplied.
| **Client Example**: ``auth_mech: :scram256``
| **Connection URI Example**: ``authMechanism=SCRAM-SHA-256``

Expand Down
4 changes: 0 additions & 4 deletions source/connect/stable-api.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,6 @@ Stable API
.. meta::
:keywords: compatible, backwards, upgrade

.. note::

The Stable API feature requires {+mdb-server+} 5.0 or later.

Comment on lines -20 to -23
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For https://github.com/10gen/docs-mongodb-internal/pull/13731/

Overview
--------

Expand Down
5 changes: 0 additions & 5 deletions source/data-formats/time-series.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,11 +58,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.

Comment on lines -61 to -65
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For https://github.com/10gen/docs-mongodb-internal/pull/13731

To create a time series collection, you must pass an options hash that contains
the specifications for the collection. You can specify the following specifications
for your time series collection:
Expand Down
54 changes: 0 additions & 54 deletions source/includes/mongodb-compatibility-table-ruby.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,114 +7,60 @@
- MongoDB 8.0
- MongoDB 7.0
- MongoDB 6.0
- MongoDB 5.0
- MongoDB 4.4
- MongoDB 4.2
- MongoDB 4.0

* - 2.21
- |checkmark|
- |checkmark|
- |checkmark|
- |checkmark|
- |checkmark|
- |checkmark|
- |checkmark|

* - 2.19 to 2.20
-
- |checkmark|
- |checkmark|
- |checkmark|
- |checkmark|
- |checkmark|
- |checkmark|

* - 2.18
-
-
- |checkmark|
- |checkmark|
- |checkmark|
- |checkmark|
- |checkmark|

* - 2.17
-
-
-
- |checkmark|
- |checkmark|
- |checkmark|
- |checkmark|

* - 2.16
-
-
-
- |checkmark|
- |checkmark|
- |checkmark|
- |checkmark|

* - 2.14 to 2.15
-
-
-
-
- |checkmark|
- |checkmark|
- |checkmark|

* - 2.13
-
-
-
-
- |checkmark| [#ocsp]_
- |checkmark|
- |checkmark|

* - 2.12
-
-
-
-
-
- |checkmark|
- |checkmark|

* - 2.11
-
-
-
-
-
- |checkmark| [#client-side-encryption]_
- |checkmark|

* - 2.10
-
-
-
-
-
- |checkmark| [#srv-polling]_ [#client-side-encryption]_
- |checkmark|

* - 2.6 to 2.9
-
-
-
-
-
-
- |checkmark|

.. [#ocsp] OCSP verification is implemented as of driver version 2.14.
.. [#srv-polling] Polling of SRV records in sharded topologies is
implemented as of driver version 2.11.
.. [#client-side-encryption] Client-side encryption is implemented as of
driver version 2.12.

.. include:: /includes/unicode-checkmark.rst
2 changes: 0 additions & 2 deletions source/read/collations.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,6 @@ Collations
Overview
--------

.. versionadded:: 3.4

Collations are sets of rules for how to compare strings, typically in a
particular natural language.

Expand Down
5 changes: 0 additions & 5 deletions source/security/auth-mechanisms/aws-iam.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,11 +20,6 @@ AWS Identity and Access Management
Overview
--------

.. note::

AWS authentication is available only in the MongoDB Enterprise Edition for MongoDB 4.4
and later.

Comment on lines -23 to -27
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For https://github.com/10gen/docs-mongodb-internal/pull/13731

The AWS authentication mechanism uses AWS `Identity and Access Management (IAM)
<https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html>`_
and AWS `Security Token Service (STS)
Expand Down
5 changes: 2 additions & 3 deletions source/security/auth-mechanisms/scram.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,8 @@ Overview
**Salted Challenge Response Authentication Mechanism (SCRAM)** is a family of
authentication mechanisms that use a challenge-response mechanism to authenticate
the user. SCRAM-SHA-256, which uses the SHA-256 algorithm to hash your password, is the
default authentication mechanism in {+mdb-server+} version 4.0
and later. SCRAM-SHA-1, which uses the SHA-1 algorithm instead, is the default
authentication mechanism in {+mdb-server+} versions earlier than 4.0.
default authentication mechanism in {+mdb-server+} version 6.0
and later.

You can use SCRAM to authenticate to MongoDB Atlas, MongoDB
Enterprise Advanced, and MongoDB Community Edition.
Expand Down
7 changes: 3 additions & 4 deletions source/security/in-use-encryption.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,10 +73,9 @@ Encryption </core/queryable-encryption/>` in the {+mdb-server+} manual.
Client-side Field Level Encryption
----------------------------------

Client-side Field Level Encryption (CSFLE) was introduced in {+mdb-server+}
version 4.2 and supports searching encrypted fields for equality.
CSFLE differs from Queryable Encryption in that you can select either a
deterministic or random encryption algorithm to encrypt fields. You can only
Client-side Field Level Encryption (CSFLE) supports searching encrypted fields
for equality. CSFLE differs from Queryable Encryption in that you can select either
a deterministic or random encryption algorithm to encrypt fields. You can only
query encrypted fields that use a deterministic encryption algorithm when
using CSFLE. When you use a random encryption algorithm to encrypt
fields in CSFLE, they can be decrypted, but you cannot perform equality
Expand Down
Loading