Ship a patch release

[Shnatsel]

As previously discussed on Matrix, now is a good time to ship a new patch release. It's been 5 months since the last release. And next GNOME release is shipping mid-September, so we should publish soon if we want all the recent fixes to be picked up by distros that will ship Glycin.

We can then start work on the next semver-breaking release in main.

Is there anything we want to land before that, or are we good to go?

[fintelia]

I think it would be good to get a release out with what we've got now. We've got some significant improvements to TIFF decoding and build times that have been waiting for a while.

Then it might make sense to do another release in the 0.25.x with the remaining in-progress work:

• Add decoding hooks #2372 and Implement Cicp for ImageBuffer,DynamicImage and provide ColorTransform on moxcms #2531 would be good so we can get experience with those APIs and find out if there's anything to change for 1.0
• Upgrade to png 0.18.0 (hasn't been released yet, but I think might be just about ready?)

[Shnatsel]

Do you want to publish subcrates like webp and tiff at the same time and make image depend on these new releases? This would save Glycin a lot of hassle dealing with bug reports that are already fixed in the latest versions.

[fintelia]

Publishing subcrates at the same time seems good, but I prefer not to bump the minimum required versions at the same time when possible. If something goes wrong with a subcrate and we have to yank it to investigate (or even just want to compare behavior between old and new), it is easier if the image crate can work with multiple versions of the subcrate

[Shnatsel]

I went ahead and wrote the changelogs to make actually shipping everything easier:

#2555

image-rs/image-tiff#291

image-rs/image-webp#157