# POST /api/v1/pods stops working

Calls to POST /api/v1/pods on CocoaPods Trunk API stop working on December 2, 2026.

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.

- API: CocoaPods Trunk API (trunk.cocoapods.org)
- Kind: Endpoint removal
- Takes effect: December 2, 2026
- Calls after that day: fail
- Calls it hits: `POST /api/v1/pods`
- Source: [Announcement](https://blog.cocoapods.org/CocoaPods-Specs-Repo/)
- Page: https://www.okapi.bot/providers/cocoapods-trunk-api/breaking-changes/post-api-v1-pods-stops-working/

## What to use instead

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.

## 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.