Repository navigation
chore: Remove CocoaPods distribution support - #464
Merged
Merged
Conversation
philprime
marked this pull request as ready for review
October 11, 2026 15:49
philprime
enabled auto-merge (squash)
October 11, 2026 15:49
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove CocoaPods distribution support, including the podspec, example app, installation instructions, badge, and tooling references. Keep Swift Package Manager, Carthage, and the existing XCFramework release workflow unchanged.
Remaining dependency
CocoaPods remains in the Ruby lockfile only because Jazzy requires it transitively. Removing it entirely requires replacing the documentation generator.
Verification
make test-macospassed with 243 unit tests and 21 integration tests.make lint,git diff --check, and commit hooks passed. Restored the disabled testing flag after testing. Only macOS was tested. Invalid-PDF coverage emitted a CoreGraphics diagnostic without test failures.