push-auth

The provider JWTs push adapters sign: ES256 for APNs and VAPID, RS256 for Google, with a keyed cache.

With cargo

cargo add cratefield-push-auth

What it is

push-auth.

Provider-JWT signing for push adapters: ES256 (APNs, VAPID) and RS256 (Google service accounts), with a keyed token cache.

From the crate’s own Cargo.toml description.

History

From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 4 versions recorded, newest first. Every published version is on crates.io.

0.3.2
19 Oct 2026crates.io Release Diff
Other
- updated the following local packages: cratefield-core
0.3.1
15 Oct 2026crates.io Release Diff
Other
- updated the following local packages: cratefield-core

2 earlier versions 0.2.1 to 0.3.0

0.3.0
4 Oct 2026crates.io Release Diff
Changed
- Breaking: requires cratefield-core 0.8 (was 0.7), and so a minor rather than a patch bump: a venture still on core 0.7 does not pick this release up through a caret requirement and end up with two copies of core (#712).
Other
- updated the following local packages: cratefield-core
0.2.1
3 Oct 2026crates.io Release
Other
- updated the following local packages: cratefield-core

One of 76 crates in the harness, all of them MIT and all of them in one repository.