BUG: Moved release note and changed test pandas-dev#43784

Author: KingOfTheShow69

doc/source/whatsnew/v1.5.0.rst

@@ -995,7 +995,6 @@ Datetimelike
 - Bug in :class:`Timestamp` with an integer or float value and ``unit="Y"`` or ``unit="M"`` giving slightly-wrong results (:issue:`47266`)
 - Bug in :class:`.DatetimeArray` construction when passed another :class:`.DatetimeArray` and ``freq=None`` incorrectly inferring the freq from the given array (:issue:`47296`)
 - Bug when adding a :class:`DateOffset` to a :class:`Series` would not add the ``nanoseconds`` field (:issue:`47856`)
-- Bug where adding a :class:`DateOffset` to a :class:`DatetimeIndex` or :class:`Series` over a Daylight Savings Time boundary would produce an incorrect result (:issue:`43784`)
 - Bug in :func:`to_datetime` where ``OutOfBoundsDatetime`` would be thrown even if ``errors=coerce`` if there were more than 50 rows (:issue:`45319`)
 -
 

doc/source/whatsnew/v1.6.0.rst

@@ -127,6 +127,7 @@ Categorical
 Datetimelike
 ^^^^^^^^^^^^
 - Bug in :func:`pandas.infer_freq`, raising ``TypeError`` when inferred on :class:`RangeIndex` (:issue:`47084`)
+- Bug where adding a :class:`DateOffset` to a :class:`DatetimeIndex` or :class:`Series` over a Daylight Savings Time boundary would produce an incorrect result (:issue:`43784`)
 -
 
 Timedelta

pandas/tests/tseries/offsets/test_dst.py

@@ -251,6 +251,9 @@ def test_series_dst_addition():
         [Timestamp("2020-10-26 00:00:00+01:00"), Timestamp("2017-03-13 00:00:00-07:00")]
     )
 
-    tm.assert_series_equal((startdates + offset1), expected1)
+    result1 = startdates + offset1
+    result2 = startdates + offset2
 
-    tm.assert_series_equal((startdates + offset2), expected2)
+    tm.assert_series_equal(result1, expected1)
+
+    tm.assert_series_equal(result2, expected2)