Hotfix 23.10 - cudf, dask-cudf and cugraph (#452)

23.10 Hot-fix to correct cudf 23.10.1 that introduced a nasty regression
that affects both dask_cudf=23.10 and cugraph=23.10

---------

Co-authored-by: aravenel <[email protected]>
Co-authored-by: Nick Becker <[email protected]>

_notices/rgn0030.md

@@ -0,0 +1,38 @@
+---
+layout: notice
+parent: RAPIDS General Notices
+grand_parent: RAPIDS Notices
+nav_exclude: true
+notice_type: rgn
+# Update meta-data for notice
+notice_id: 30 # should match notice number
+notice_pin: false # set to true to pin to notice page
+title: "RAPIDS v23.10 Hotfix for cuDF"
+notice_author: RAPIDS TPM
+notice_status: Completed
+notice_status_color: green
+# 'notice_status' and 'notice_status_color' combinations:
+#   "Proposal" - "blue"
+#   "Completed" - "green"
+#   "Review" - "purple"
+#   "In Progress" - "yellow"
+#   "Closed" - "red"
+notice_topic: Release Change
+notice_rapids_version: "v23.10"
+notice_created: 2023-11-20
+# 'notice_updated' should match 'notice_created' until an update is made
+notice_updated: 2023-11-20
+---
+
+## Overview
+
+`cudf 23.10.01` introduced a bug that could cause incorrect output in `cudf` and `dask-cudf` when merging dataframes in which one of the indexes is not unique. `cudf` is being hotfixed to `23.10.02` to resolve this issue.
+
+## Rationale
+
+`cudf 23.10.01` introduced a bug that could cause incorrect output in `cudf` and `dask-cudf` when merging dataframes in which one of the indexes is not unique. `cudf` is being hotfixed to `23.10.02` to resolve this issue. The issue is not present in `cudf 23.12` nightlies.
+
+
+## Impact
+
+All `cudf` and `dask-cudf` users are encouraged to upgrade to the new `23.10.02` patch release.