0.15.4 prep: linux arm64 packaging, rustls 0.23.45

[cpu]

• Try the CI caching improvements from ci: use targeted Rust build caches rcgen#458 for the artifact builds in this repo
• Add Linux arm64 artifact packaging (requested downstream by curl for their CI).
• Update from rustls 0.23.42 -> 0.23.45 (notably taking the fix for GHSA-2mjx-qc3c-rqvc). This also brings the updated MLDSA support for the aws-lc-rs provider builds.
• Updates version to 0.15.4 and updates changelog.

[cpu]

Note: this is also a small bugfix (in cbindgen.toml), we were shifting in _MINOR twice before 😮‍💨

[djc]

Why 22.04 for ARM?

[cpu]

Why 22.04 for ARM?

Matching the other pre-existing artifact production jobs where we've avoided using the -latest that shifts unpredictably:

rustls-ffi/.github/workflows/artifacts.yaml

Lines 16 to 17 in 60d5127

	name: Windows (x86_64 MSVC)
	runs-on: windows-2022 # x86_64

rustls-ffi/.github/workflows/artifacts.yaml

Lines 50 to 51 in 60d5127

	name: Linux (x86_64 GNU)
	runs-on: ubuntu-22.04 # x86_64.

rustls-ffi/.github/workflows/artifacts.yaml

Lines 81 to 82 in 60d5127

	name: Linux (x86-64 GNU Deb)
	runs-on: ubuntu-22.04 # x86_64.

rustls-ffi/.github/workflows/artifacts.yaml

Lines 116 to 117 in 60d5127

	name: MacOS (Arm64 and x86_64)
	runs-on: macos-14 # arm64.

[djc]

Fair enough!

Was asking because some of the artifact builds do also just use -latest.

[cpu]

Was asking because some of the artifact builds do also just use -latest.

It's a fair question. I think only the ones that test the artifacts produced by the earlier stages use -latest. I can't remember why I thought that was helpful, but it seemed like a good idea at the time 😆

[cpu]

• Created 0.15.4 github tag
• Published rustls-ffi v0.15.4 at registry crates-io
• Created 0.15.4 github release
• Attached artifacts to release.