Tag `3.2-1` release, or give another way to follow new releases for packagers

[ilyagr]

According to https://github.com/garabik/unicode/blob/master/debian/changelog, there have been a few releases since 2.9, including the important 3.2-1 release that enables the use of unicode with Python 3.13 (solving https://github.com/garabik/unicode/issues/26, see also https://github.com/garabik/unicode/issues/26#issuecomment-3016027610). However, 2.9 is currently the latest release tagged in GitHub (both in https://github.com/garabik/unicode/tags and in https://github.com/garabik/unicode/releases).

Would it be possible to tag the latest release in GitHub? This would make it much easier to update the unicode-paracode package in nixpkgs, solving https://github.com/NixOS/nixpkgs/issues/419447 (which is already set up to auto-update whenever a release is tagged on GitHub). It would also help all other packagers to know which commit to package.

Or, is there another good solution?

[ilmari]

It would be useful to have the 3.2 release uploaded to PyPI as well.