Skip to content

Allow Crypto 5 in the APNS 6.6 compatibility branch - #1

Draft
jsflax wants to merge 1 commit into
codex/6.6-compatibility-basefrom
codex/hud-crypto5-backport
Draft

jsflax wants to merge 1 commit into
codex/6.6-compatibility-basefrom
codex/hud-crypto5-backport

Conversation

@jsflax

@jsflax jsflax commented Nov 3, 2026 •

Copy link
Copy Markdown
Owner

APNS 6.6 excludes Crypto 5, preventing its use with our existing Crypto 5.0.3 dependency graph. Widen both the standard and Swift 5.10 manifests to 3.0.0..<6.0.0 while preserving the APNS 6.6 API, targets, and platform minimums. This backports the range change from upstream #272 without adopting the later macOS 15 requirement.

Keep the existing authentication tests and add a regression that verifies a token manager JWT with its P256 public key and rejects a changed payload.

Based on exact 6.6.0 commit 81eb92b6d5cbea9dac154becedf316c05189a47a. Source verification confirms the complete 116-file tree differs only in the two manifests and authentication test file. Local tests were not run for this publication; no cloud checks have started in this new fork as of publication. CI settings and policies were left unchanged.

@jsflax jsflax closed this Nov 3, 2026
@jsflax jsflax reopened this Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant