IIUC, I should add a file doc/release/upcoming_changes/24680.new_feature.rst with contents like

``strict`` option for `testing.assert_allclose`
-----------------------------------------------
The ``strict`` option is now available for `testing.assert_allclose`.
Setting ``strict=True`` will disable the broadcasting behaviour for scalars and
ensure that input arrays have the same data type.

? I'll also commit the <BLANKLINE>s above and run CI with [skip actions] [skip cirrus] [skip azp]?

That seems about right, yes.

@mdhaber Please go ahead and commit your self-review changes so we can get this in.

Thanks @mattip. That rendered as intended.
When this merges, shall I do the same for assert_equal?

Thanks @mdhaber. Yes, I think assert_equal could also get a strict kwarg. At the same time, the docstring of assert_equal could use some touchup: it is missing the Notes and See Also that the others have.

@mattip I opened gh-24770 to add the strict kwarg to assert_equal and touch up the docs as you suggested. gh-24775 adds strict to assert_array_less.