(DOCS-15655): 5.0.13 changelog (#1922)

* (DOCS-15655): 5.0.13 changelog (#1921)

* update snooty.toml

Author: jeff-allen-mongo

snooty.toml

@@ -207,7 +207,7 @@ windows-dir-version = "5.0" # wizard
 package-name-org = "mongodb-org"
 package-name-enterprise = "mongodb-enterprise"
 version = "5.0"
-release = "5.0.12"
+release = "5.0.13"
 version-dev = "5.3"
 pgp-version = "{+version+}"
 rsa-key = "4B7C549A058F8B6B"

source/includes/changelogs/releases/5.0.13.rst

@@ -0,0 +1,54 @@
+.. _5.0.13-changelog:
+
+5.0.13 Changelog
+----------------
+
+Sharding
+~~~~~~~~
+
+- :issue:`SERVER-68094` Resharding with custom generated _id fails with projection error
+- :issue:`SERVER-68139` Resharding command fails if the projection sort is bigger than 100MB
+- :issue:`SERVER-68869` A retry of _configSvrReshardCollection can succeed causing resharding_coordinator_recovers_abort_decision.js to fail
+- :issue:`SERVER-69142` A retry of _shardsvrReshardCollection can cause DuplicateKey error (resharding_nonblocking_coordinator_rebuild.js)
+- :issue:`SERVER-69220` refineCollectionShardKey permits toggling current shard key fields between range-based and hashed, leading to data inconsistency
+- :issue:`SERVER-69384` Fix v5.0 legacy shardCollection path for implicitCreateIndex parameter
+- :issue:`SERVER-69700` Replication rollback fails resharding_coordinator_recovers_abort_decision.js
+
+Write Operations
+~~~~~~~~~~~~~~~~
+
+:issue:`SERVER-50454` Avoiding sending the "keyValue" field to drivers on duplicate key error
+
+Internals
+~~~~~~~~~
+
+- :issue:`SERVER-58673` Enable featureFlagPerShardCursor
+- :issue:`SERVER-60551` Occasionally getting "Initialized wire specification" when connecting
+- :issue:`SERVER-61185` Use prefix_search for unique index lookup
+- :issue:`SERVER-62400` Add $_passthroughToShard parameter to AggregateCommandRequest
+- :issue:`SERVER-62681` Create change streams per shard cursor passthrough suite
+- :issue:`SERVER-62738` Give mongos the ability to passthrough to a specific shard
+- :issue:`SERVER-63772` Post Batch Resume token not sent on initial batch from per shard cursor change stream
+- :issue:`SERVER-63773` Per Shard cursor post batch resume token not set in getMore responses
+- :issue:`SERVER-63774` Pass optional dbVersion to runPipelineOnSpecificShard
+- :issue:`SERVER-63781` $sortKey not filtered out in initial batch from post batch resume token
+- :issue:`SERVER-65006` Write conflict on commitIndexBuild oplog entry insertion can cause multikey to fail to be set
+- :issue:`SERVER-66794` Add an in-memory flag for TS collections having dates outside years 1970-2038
+- :issue:`SERVER-67402` Linearizable reads can occasionally read with wrong read source
+- :issue:`SERVER-67538` Multi-doc transactions should fail if on an old, incompatible snapshot
+- :issue:`SERVER-67650` Resharding recipient can return remainingOperationTimeEstimatedSecs=0 when the oplog applier hasn't caught up with the oplog fetcher
+- :issue:`SERVER-67653` Resharding coordinator can incorrectly conclude that it can start the critical section although on one recipient the oplog applier hasn't caught up with the oplog fetcher
+- :issue:`SERVER-67725` Check catalog consistency on shards as precondition for rename
+- :issue:`SERVER-67916` Race during stepdown can trigger invariant in ReshardingMetrics
+- :issue:`SERVER-68003` Make experiment_unified_ninja.vars the default
+- :issue:`SERVER-68126` Check for negative maxChunkSize input value in AutoSplitVector 
+- :issue:`SERVER-68691` $graphLookup does not report variable references for 'restrictSearchWithMatch' filter
+- :issue:`SERVER-69002` [5.0] backport pm-2419 Per Shard Cursors via mongos
+- :issue:`SERVER-69108` SCCL can immediately return config and admin metadata without triggering a refresh
+- :issue:`SERVER-69547` Add multiversion_incompatible tag to show_raw_update_description*.js
+- :issue:`SERVER-69590` libunwind warnings on clang arm platforms
+- :issue:`SERVER-69611` Set the -ffp-contract=off compiler option by default
+- :issue:`SERVER-69693` Use lambda instead of repeating code in resharding coordinator
+- :issue:`SERVER-69785` robustify change_streams_per_shard_cursor.js
+- :issue:`WT-9870` Fix updating pinned timestamp whenever oldest timestamp is updated during recovery
+

source/release-notes/5.0-changelog.txt

@@ -10,6 +10,8 @@
    :depth: 1
    :class: singlecol
 
+.. include:: /includes/changelogs/releases/5.0.13.rst
+
 .. include:: /includes/changelogs/releases/5.0.12.rst
 
 .. include:: /includes/changelogs/releases/5.0.11.rst

source/release-notes/5.0.txt

@@ -17,6 +17,31 @@ Release Notes for MongoDB 5.0
 Patch Releases
 --------------
 
+.. _5.0.13-release-notes:
+
+5.0.13 - Sep 29, 2022
+~~~~~~~~~~~~~~~~~~~~~
+
+Issues fixed:
+
+- :issue:`SERVER-69611` Set the -ffp-contract=off compiler option by
+  default
+- :issue:`SERVER-69220` refineCollectionShardKey permits toggling
+  current shard key fields between range-based and hashed, leading to
+  data inconsistency
+- :issue:`SERVER-67650` Resharding recipient can return
+  remainingOperationTimeEstimatedSecs=0 when the oplog applier hasn't
+  caught up with the oplog fetcher
+- :issue:`SERVER-68094` Resharding with custom generated _id fails with
+  projection error
+- :issue:`WT-9870` Fix updating pinned timestamp whenever oldest
+  timestamp is updated during recovery
+
+- `All JIRA issues closed in 5.0.13
+  <https://jira.mongodb.org/issues/?jql=project%20in%20(SERVER%2C%20TOOLS%2C%20WT)%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%205.0.13>`_
+
+- :ref:`5.0.13-changelog`
+
 .. _5.0.12-release-notes:
 
 5.0.12 - Sep 05, 2022