What it is
adapter-github-app.
GitHub App authentication for the Cratefield harness (issue #623). It turns an App's private key into the credentials the GitHub REST API accepts, over the runtime's HttpClient and Clock ports — no vendor SDK, no reqwest, no tokio, no std::time — so the same client runs on Cloudflare Workers and natively (ADR 0002: the ports are core's, the vendor client is this crate's). Signing reuses cratefield-push-auth's Rs256Signer and its keyed CachedToken, the same verified stack the push adapters present.
From the crate’s own README.
History
Changelog.
From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 4 versions recorded, newest first. Every published version is on crates.io.
Other
- updated the following local packages: cratefield-core, cratefield-push-auth
Other
- updated the following local packages: cratefield-core
2 earlier versions 0.1.0 to 0.2.0
Changed
- Breaking: requires
cratefield-core0.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
- Breaking: requires
One of 76 crates in the harness, all of them MIT and all of them in one repository.