Release preparation

[jmcnamara]

Discussion node to co-ordinate calamine releases.

[jmcnamara]

@jqnatividad @Expurple @sftse

I am going to start prepping the v0.32.0 release of Calamine for later today.

[jmcnamara]

Calamine v0.32.0 has been released:

• https://crates.io/crates/calamine
• https://github.com/tafia/calamine/releases/tag/v0.32.0
• https://docs.rs/calamine/latest/calamine/changelog/index.html

Thanks to all the contributors and welcome to @louisdewar who was a new contributor in the release.

[jmcnamara]

For the next release the following dependency versions could be updated:

$ cargo upgrade -i --dry-run
    Checking calamine's dependencies
name      old req compatible latest new req
====      ======= ========== ====== =======
codepage  0.1.1   0.1.2      0.1.2  0.1.2  
atoi_simd 0.16    0.16.1     0.17.0 0.17   
zip       4.2.0   4.6.1      6.0.0  6.0.0  
sha2      0.10.8  0.10.9     0.10.9 0.10.9 
rstest    0.21.0  0.21.0     0.26.1 0.26.1 

If anyone has opinions on whether some/all of these should or shouldn't be updated please shout.

[jqnatividad]

For me, I go with the latest by default.

Though, I've made exceptions for crates like zip (they went through some version churn earlier this year - introducing non semver compliant breaking changes, so I pinned to 4.x for a while, before finally making the jump to 6.x after wider adoption) and atoi_simd (currently staying with 0.16, as 0.17 is not yet adopted by a major dependency I have - i.e. polars).

WIth that said, my vote is to go with the latest for all crates except atoi_simd, specifying only up to the minor version, if possible.

[jmcnamara]

WIth that said, my vote is to go with the latest for all crates except atoi_simd, specifying only up to the minor version, if possible.

Agreed. I will update those closer to the next release.

[jmcnamara]

@jqnatividad For the next release I would also like to enable additional clippy checks, like you suggested here:

#578 (comment)

[sftse]

dependency update LGTM