CocoaPods Trunk API
POST /api/v1/pods endpoint removal
Stops workingSubscribe to CocoaPods Trunk APIShare
On December 2, 2026, CocoaPods Trunk will become read-only and will stop accepting new versions or pods. Calls to POST /api/v1/pods will fail after that day. Existing pods will continue to install, but no new Podspecs can be published to trunk.
Calls it hits
POST /api/v1/pods
What to use instead of these calls
Publish new versions elsewhere by distributing your library as a Swift Package with a Package.swift in its Git repository or through a private CocoaPods specs repository. Maintainers must decide on an alternative distribution strategy, as trunk will not accept new Podspecs.
Trunk takes no new Podspecs after the switch: publishing moves to Swift Package Manager or a private specs repo, a distribution choice for the maintainers.
In CocoaPods Trunk API's words
TLDR: In two years we plan to turn CocoaPods trunk to be read-only. At that point, no new versions or pods will be added to trunk.
Facts
- API
- CocoaPods Trunk API
trunk.cocoapods.org - Kind
- Endpoint removal
- Takes effect
- December 2, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against CocoaPods Trunk API's own pages
Questions
When does this change take effect?
Calls to POST /api/v1/pods on CocoaPods Trunk API stop working on December 2, 2026.
What happens to calls after December 2, 2026?
They fail from that day.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before December 2, 2026.