mongodb
diff --git a/‎config/redirects
Lines changed: 5 additions & 2 deletions b/‎config/redirects
Lines changed: 5 additions & 2 deletions
diff --git a/‎snooty.toml
Lines changed: 4 additions & 3 deletions b/‎snooty.toml
Lines changed: 4 additions & 3 deletions
diff --git a/‎source/core/hashed-sharding.txt
Lines changed: 17 additions & 15 deletions b/‎source/core/hashed-sharding.txt
Lines changed: 17 additions & 15 deletions
diff --git a/‎source/core/sharded-cluster-query-router.txt
Lines changed: 12 additions & 4 deletions b/‎source/core/sharded-cluster-query-router.txt
Lines changed: 12 additions & 4 deletions
diff --git a/‎source/includes/bulkWrite-introduction.rst
Lines changed: 5 additions & 0 deletions b/‎source/includes/bulkWrite-introduction.rst
Lines changed: 5 additions & 0 deletions
diff --git a/‎source/includes/bulkWrite-multi-field.rst
Lines changed: 5 additions & 0 deletions b/‎source/includes/bulkWrite-multi-field.rst
Lines changed: 5 additions & 0 deletions
diff --git a/‎source/includes/changelogs/releases/4.4.26.rst
Lines changed: 1 addition & 0 deletions b/‎source/includes/changelogs/releases/4.4.26.rst
Lines changed: 1 addition & 0 deletions
diff --git a/‎source/includes/changelogs/releases/6.0.12.rst
Lines changed: 1 addition & 0 deletions b/‎source/includes/changelogs/releases/6.0.12.rst
Lines changed: 1 addition & 0 deletions
diff --git a/‎source/includes/changelogs/releases/7.1.1.rst
Lines changed: 4 additions & 0 deletions b/‎source/includes/changelogs/releases/7.1.1.rst
Lines changed: 4 additions & 0 deletions
diff --git a/‎source/includes/fact-encryption-options-create-collection.rst
Lines changed: 4 additions & 0 deletions b/‎source/includes/fact-encryption-options-create-collection.rst
Lines changed: 4 additions & 0 deletions
@@ -1,11 +1,11 @@
 define: prefix docs
 define: base https://www.mongodb.com/${prefix}
 define: versions v2.2 v2.4 v2.6 v3.0 v3.2 v3.4 v3.6 v4.0 v4.2 v4.4 v5.0 v5.1 v5.2 v5.3 v6.0 v6.1 v6.2 v6.3 v7.0 v7.1 master
-symlink: master -> v7.1
+symlink: master -> v7.2
 symlink: stable -> v7.0
 symlink: rapid -> v7.1
 symlink: current -> v7.0
-symlink: upcoming -> v7.1
+symlink: upcoming -> v7.2
 symlink: manual -> v7.0
 
 [v2.2]: ${prefix}/${version}/core/read-operations-introduction -> ${base}/${version}/core/read-operations/
@@ -2538,6 +2538,9 @@ raw: ${prefix}/${version}/applications/drivers -> ${base}/drivers/
 # DOCSP-32198 Redirect removed page
 [v7.0-*]: ${prefix}/${version}/tutorial/upgrade-revision -> ${base}/${version}/release-notes/
 
+## DOCSP-29667 New page for bulkWrite
+[*-v7.1): ${prefix}/${version}/reference/command/bulkWrite -> ${base}/${version}/reference/command/
+
 # DOCSP-31908 Removing free monitoring pages after decomission
 [*]: ${prefix}/${version}/reference/method/db.enableFreeMonitoring -> ${base}/${version}/administration/free-monitoring/
 [*]: ${prefix}/${version}/reference/method/db.disableFreeMonitoring -> ${base}/${version}/administration/free-monitoring/
 
@@ -204,6 +204,7 @@ toc_landing_pages = [
    "/release-notes/6.3",
    "/release-notes/7.0",
    "/release-notes/7.1",
+   "/release-notes/7.2",
    "/replication",
    "/security",
    "/sharding",
@@ -241,7 +242,7 @@ sbe-short = "slot-based execution engine"
 sbe-title = "Slot-Based Query Execution Engine"
 version = "{+version+}"
 version-last = "{+version-last+}"
-year = "2022"
+year = "2023"
 ui-org-menu = ":icon-mms:`office` :guilabel:`Organizations` menu"
 
 [constants]
@@ -254,11 +255,11 @@ windows-dir-version = "6.0" # wizard
 package-name-org = "mongodb-org"
 package-name-enterprise = "mongodb-enterprise"
 package-name = "mongodb"
-version = "7.1"
+version = "7.3"
 latest-lts-version = "7.0"
 last-supported-version = "5.0"
 release = "7.1.1"
-version-dev = "7.1"
+version-dev = "7.2"
 version-last = "6.0"
 pgp-version = "{+version+}"
 rsa-key = "4B7C549A058F8B6B"
 
@@ -138,6 +138,8 @@ If you shard a populated collection using a hashed shard key:
 - After the initial chunk creation, the balancer moves ranges of the
   initial chunk when it needs to balance data.
 
+.. _shard-empty-collection:
+
 Shard an Empty Collection
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -147,20 +149,19 @@ Sharding Empty Collection on Single Field Hashed Shard Key
   - With no :ref:`zones and zone ranges <zones-sharding>` specified 
     for the empty or non-existing collection:
 
-    - The sharding operation creates empty chunks to cover the entire
-      range of the shard key values and performs an initial chunk
-      distribution. By default, the operation creates 2 chunks per shard
-      and migrates across the cluster. You can use ``numInitialChunks``
-      option to specify a different number of initial chunks. This
-      initial creation and distribution of chunks allows for faster
-      setup of sharding.
+    - The sharding operation creates an empty chunk to cover the entire
+      range of the shard key values. Starting in version 7.2, the
+      operation creates 1 chunk per shard by default and migrates
+      across the cluster. You can use ``numInitialChunks`` option to
+      specify a different number of initial chunks and cause an initial
+      chunk distribution. This initial creation and distribution of
+      chunks allows for faster setup of sharding.
 
     - After the initial distribution, the balancer manages the chunk
       distribution going forward.
 
   - With zones and zone ranges specified
-    for the empty or a non-existing collection (Available starting in 
-    MongoDB 4.0.3):
+    for the empty or a non-existing collection:
 
     - The sharding operation creates empty chunks for the defined zone
       ranges as well as any additional chunks to cover the entire range
@@ -173,19 +174,20 @@ Sharding Empty Collection on Single Field Hashed Shard Key
 
 Sharding Empty Collection on Compound Hashed Shard Key with Hashed Field Prefix
   If the compound hashed shard key has the hashed field as the prefix
-  (i.e. the hashed field is the first field in the shard key):
+  (the hashed field is the first field in the shard key):
 
   - With no zones and zone ranges specified 
     for the empty or non-existing collection:
 
     - The sharding operation creates empty chunks to cover the entire
       range of the shard key values and performs an initial chunk
       distribution. The value of all non-hashed fields is :bsontype:`MinKey` at
-      each split point. By default, the operation creates 2 chunks per
-      shard and migrates across the cluster. You can use
-      ``numInitialChunks`` option to specify a different number of
-      initial chunks. This initial creation and distribution of chunks
-      allows for faster setup of sharding.
+      each split point. Starting in version 7.2, the operation creates
+      1 chunk per shard by default and migrates across the cluster. You
+      can use ``numInitialChunks`` option to specify a different number
+      of initial chunks and cause an initial chunk distribution. This
+      initial creation and distribution of chunks allows for faster
+      setup of sharding.
 
     - After the initial distribution, the balancer manages the chunk
       distribution going forward.
 
@@ -70,10 +70,18 @@ randomly-selected shard in the set of shards targeted by the aggregation.
 For more information on how the work of aggregation is split among
 components of a sharded cluster query, use ``explain:true`` as a
 parameter to the :method:`~db.collection.aggregate()` call. The
-return includes three json objects. ``mergeType`` shows where the
-stage of the merge happens ("primaryShard", "anyShard", or "mongos").
-``splitPipeline`` shows which operations in your pipeline have run on
-individual shards. ``shards`` shows the work each shard has done.
+return includes three JSON objects: 
+
+- ``mergeType`` shows where the
+  stage of the merge happens ("primaryShard", "anyShard", "specificShard", 
+  or "mongos"). When ``mergeType`` is ``specificShard``, the aggregate 
+  output includes a ``mergeShard`` property that contains the shard ID of the 
+  merging shard. 
+
+- ``splitPipeline`` shows which operations in your pipeline have 
+  run on individual shards. 
+
+- ``shards`` shows the work each shard has done.
 
 In some cases, when the :term:`shard key` or a prefix of the shard key
 is a part of the query, the :binary:`~bin.mongos` performs a
 
@@ -0,0 +1,5 @@
+Starting in MongoDB 7.2, you can use the new :dbcommand:`bulkWrite`
+command to perform many insert, update, and delete operations on
+multiple collections in one request. The existing
+:method:`db.collection.bulkWrite` method only allows you to modify one
+collection in one request.
@@ -0,0 +1,5 @@
+If the ``multi`` field is ``true``, the update or delete operation
+updates or deletes all documents that match the document ``filter``. If
+``false``, the operation updates or deletes the first document that
+matches the document ``filter``. For details on multi-document
+transactions, see :ref:`transactions`.
@@ -60,6 +60,7 @@ Internals
   10gen-to-Mongodb to syncs new commits to mongodb/mongo
 - :issue:`SERVER-82449` [v4.4] Optimize copybara sync behavior for
   specific no-change scenarios
+- :issue:`SERVER-82825` Stop copybara service to sync
 - :issue:`WT-7492` Ignore the evict drain wait msg in stdout.txt for
   test_cursor_random
 - :issue:`WT-10380` Fix expected warning output in test_cursor_random:
 
@@ -66,6 +66,7 @@ Internals
   to non-existing oplog
 - :issue:`SERVER-80886` $out may fail with a StaleDbVersion after a
   movePrimary
+- :issue:`SERVER-80901` Audit gFeatureFlagServerlessChangeStreams
 - :issue:`SERVER-80988` [6.0] Search Index Management Commands Fail To
   Detect Collection on Other Shards
 - :issue:`SERVER-81033` Ignore the collMod response from the DBPrimary
 
@@ -35,6 +35,8 @@ Internals
   collection and indexes can make the catalog inconsistent
 - :issue:`SERVER-81028` Incorrect $listCatalog behavior in presence of a
   concurrent collection rename in v7.0
+- :issue:`SERVER-81033` Ignore the collMod response from the DBPrimary
+  shard if it has no chunks
 - :issue:`SERVER-81049` Move queryStatsRead and
   queryStatsReadTransformed privileges into clusterMonitor builtin role
 - :issue:`SERVER-81106` Recipient shard doesn't wait for the collection
@@ -50,6 +52,8 @@ Internals
   with  integration_tests_sharded suite
 - :issue:`SERVER-81343` Add NamespaceNotFound as an expected error for
   resharding on random_DDL_CRUD_operations.js
+- :issue:`SERVER-81372` Collection defragmentation phases sporadically
+  jump backward
 - :issue:`SERVER-81390` HashAggStage fails to respect the collation when
   spilling to disk
 - :issue:`SERVER-81467` Run Jepsen list-append in Evergreen
 
@@ -0,0 +1,4 @@
+Starting in MongoDB 7.2, you can't specify ``wiredTiger`` storage
+engine encryption options when you create a collection with 
+:method:`db.createCollection()`. To configure encryption for 
+the WiredTiger storage engine, see :ref:`security-encryption-at-rest`.