BUG: OverflowError when fillna on DataFrame with a pd.Timestamp (pandas-dev#61208)

Author: PedroM4rques

doc/source/whatsnew/v3.0.0.rst

@@ -648,6 +648,7 @@ Datetimelike
 - Bug in :func:`date_range` where using a negative frequency value would not include all points between the start and end values (:issue:`56147`)
 - Bug in :func:`tseries.api.guess_datetime_format` would fail to infer time format when "%Y" == "%H%M" (:issue:`57452`)
 - Bug in :func:`tseries.frequencies.to_offset` would fail to parse frequency strings starting with "LWOM" (:issue:`59218`)
+- Bug in :meth:`DataFrame.fillna` raising an `AssertionError` instead of `OutOfBoundsDatetime` when filling a `datetime64[ns]` column with an out-of-bounds timestamp (e.g., `'0001-01-01'`). Now correctly raises `OutOfBoundsDatetime`. (:issue:`61208`)
 - Bug in :meth:`DataFrame.min` and :meth:`DataFrame.max` casting ``datetime64`` and ``timedelta64`` columns to ``float64`` and losing precision (:issue:`60850`)
 - Bug in :meth:`Dataframe.agg` with df with missing values resulting in IndexError (:issue:`58810`)
 - Bug in :meth:`DatetimeIndex.is_year_start` and :meth:`DatetimeIndex.is_quarter_start` does not raise on Custom business days frequencies bigger then "1C" (:issue:`58664`)
@@ -660,7 +661,6 @@ Datetimelike
 - Bug in :meth:`to_datetime` reports incorrect index in case of any failure scenario. (:issue:`58298`)
 - Bug in :meth:`to_datetime` wrongly converts when ``arg`` is a ``np.datetime64`` object with unit of ``ps``. (:issue:`60341`)
 - Bug in setting scalar values with mismatched resolution into arrays with non-nanosecond ``datetime64``, ``timedelta64`` or :class:`DatetimeTZDtype` incorrectly truncating those scalars (:issue:`56410`)
-- Bug in :meth:`DataFrame.fillna` raising an `AssertionError` instead of `OutOfBoundsDatetime` when filling a `datetime64[ns]` column with an out-of-bounds timestamp (e.g., `'0001-01-01'`). Now correctly raises `OutOfBoundsDatetime`. (:issue:`61208`)
 
 Timedelta
 ^^^^^^^^^