v0.25.3 release preparation

[cpu]

Description

This branch targets the rel-0.25 branch, which was branched from 22702f5, the last commit on main that's semver compatible with the 0.25.2 release cut from 4730449. It backports the CCADB trust root updates from #52 to prepare v0.25.3

Proposed Release Notes

New trust anchors:

• CommScope Public Trust RSA Root-01
• CommScope Public Trust RSA Root-02
• CommScope Public Trust ECC Root-01
• CommScope Public Trust ECC Root-02
• TrustAsia Global Root CA G4
• TrustAsia Global Root CA G3

Removed trust anchors:

• Duplicated Autoridad de Certificacion Firmaprofesional CIF A62634068

[djc]

Why not branch from 22702f5? Seems a bit more clear in terms of the commit history.

[cpu]

Why not branch from 22702f5? Seems a bit more clear in terms of the commit history.

As in start the rel-0.25 branch from 22702f5? In the past when I've made the rel-xxx branches I've always branched from whatever commit was used for the most recent release in that stream, usually the one bumping the Cargo.toml version. It felt like the point releases should always pick up from where the last release left off 🤔

[djc]

As in start the rel-0.25 branch from 22702f5? In the past when I've made the rel-xxx branches I've always branched from whatever commit was used for the most recent release in that stream, usually the one bumping the Cargo.toml version. It felt like the point releases should always pick up from where the last release left off 🤔

It seems fair game to me to pick a later commit from the main branch that is still compatible with the 0.25.x range. If we make this clear in the PR description (maybe including mentioning the first PR that introduced incompatible changes), I think that would be a cleaner way of maintaining the commit history.

[cpu]

I think that's reasonable for this repo where it's very clear what commit is the delineating point between compatible/incompatible. I will adjust 👍

[cpu]

• Force pushed an updated rel-0.25 branched from 22702f5
• Updated PR desc
• Added a Cargo.toml version bump for 0.25.3.

[cpu]

• Pushed a v0.25.3 tag
• Published webpki-roots v0.25.3 at registry crates-io
• Created a GitHub release

I also noticed we were missing tags for 0.25.2, 0.25.1, and 0.25.0. I retroactively pushed all of those tags to GitHub (but haven't created GitHub releases for all of the historic tagged Cargo releases)