Ship a bugfix release

[Shnatsel]

It's been 9 months since last release, and a lot of work happened on main since then. People keep running into some of the bugs in production, see e.g. image-rs/image#2913

I have cherry-picked just the bugfixes into release-0.2.5 branch so we could ship them with minimal disruption. All 3 git cherry-picks applied without any conflicts. That branch should be ready to be cargo published.

@197g could you take a quick look at the diff and run cargo publish?

[fintelia]

I think the current state on the main branch might also be suitable to ship? #175 is still unmerged since I wasn't sure of that, but everything else should be ready and I don't think there are any semver breaks

[Shnatsel]

Ah, I see! I wasn't sure if the current main is shippable or not so I erred on the side of caution. Thanks for the info!

There's still a reason to ship a pure bugfix release first. If a release contains any new features, distros such as Debian will be prohibited from upgrading to it in any stable releases. So I wanted to ship a small-diff, purely bugfix release regardless. The WebP animation compositing issue likely affects all users of GNOME that switched to image-rs for decoding, including Fedora and Ubuntu 26.04 LTS, so I wanted to make it easy for them to get the fix.

I'd be happy to publish 0.2.6 with the current main immediately afterwards since it contains a lot of other improvements, and it would be nice to get those to users as well.

[fintelia]

That sounds good, thanks! If you have a chance, another backlog item I never got around to is that we're long overdue on a color_quant release.

[Shnatsel]

I've opened a PR for that too: image-rs/color_quant#26