Update changelog for 1.13.0

[dalthviz]

Fixes #659

As a side note, checking the RELEASE.md file Seems like it is outdated? From a quick check, seems like currently what is required, besides the Changelog update PR, is to directly create a GitHub release to trigger the release workflow, right? Also, maybe adding a mention/instructions to update the conda-forge feedstock after the release is available on PyPI could be worthy 🤔 . Anyhow, let me know if making changes to the RELEASE.md makes sense (either here or in another PR after the release) @ccordoba12 !

[ccordoba12]

From a quick check, seems like currently what is required, besides the Changelog update PR, is to directly create a GitHub release to trigger the release workflow, right?

Unfortunately, that's not working but we should fix it so the wheel and tarball are pushed automatically to PyPI. If you have time, you can take a look at that after 1.13 is released.

For now, the release needs to be done manually by tagging the commit corresponding to the Changelog update with the version name (i.e. step 4. in the Release instructions) and following the rest of the steps afterwards.

[ccordoba12]

Just a small suggestion for you @dalthviz.

[dalthviz]

I think this is ready @ccordoba12 Let me know if I should merge and proceed with the release or if there is something else to change here

[ccordoba12]

Thanks @dalthviz!

[ccordoba12]

Let me know if I should merge and proceed with the release or if there is something else to change here

I think everything is ready for the release, so please proceed with it.