✅

Hi, I am the SymPy bot (v161). I'm here to help you write a release notes entry. Please read the guide on how to write release notes.

Your release notes are in good order.

Here is what the release notes will look like:

• ntheory
  • Updated wiki link for describing deterministic Miller-Rabin test (#21765 by @jeffro256)

This will be added to https://github.com/sympy/sympy/wiki/Release-Notes-for-1.9.

#### Brief description of what is fixed or changed
Updated wiki link for describing deterministic Miller-Rabin test

#### Other comments
n/a

#### Release Notes

<!-- BEGIN RELEASE NOTES -->
* ntheory
  * Updated wiki link for describing deterministic Miller-Rabin test
<!-- END RELEASE NOTES -->

Update

The release notes on the wiki have been updated.

Benchmark results from GitHub Actions

Lower numbers are good, higher numbers are bad. A ratio less than 1
means a speed up and greater than 1 means a slowdown. Green lines
beginning with + are slowdowns (the PR is slower then master or
master is slower than the previous release). Red lines beginning
with - are speedups.

Significantly changed benchmark results (PR vs master)

Significantly changed benchmark results (master vs previous release)

       before           after         ratio
     [ed9a550f]       [bc790a20]
     <sympy-1.8^0>                 
+        901±60ms        1.75±0.1s     1.94  dsolve.TimeDsolve01.time_dsolve
-         7.71±0s        4.02±0.2s     0.52  integrate.TimeIntegrationRisch02.time_doit(100)
-         7.73±0s       3.76±0.01s     0.49  integrate.TimeIntegrationRisch02.time_doit_risch(100)
+        70.1±6μs      2.26±0.01ms    32.28  matrices.TimeDiagonalEigenvals.time_eigenvals
-     4.46±0.02ms      2.50±0.01ms     0.56  solve.TimeRationalSystem.time_linsolve(10)
-         901±3μs          584±1μs     0.65  solve.TimeRationalSystem.time_linsolve(5)
-      2.13±0.1ms      1.38±0.09ms     0.65  solve.TimeSparseSystem.time_linsolve_eqs(20)
-     3.36±0.04ms       2.02±0.1ms     0.60  solve.TimeSparseSystem.time_linsolve_eqs(30)

Full benchmark results can be found as artifacts in GitHub Actions
(click on checks at the top of the PR).

Thanks!