Repository navigation
[BREAKING] Drop CocoaPods from the install docs and release process - #100
Open
jrosendahl-opt wants to merge 1 commit into
Open
jrosendahl-opt wants to merge 1 commit into
jrosendahl-opt wants to merge 1 commit into
Conversation
CocoaPods trunk goes read-only on Dec 2, 2026, and 1.4.0 is the last version published there. The README's CocoaPods section now says so and points to SPM, whose example moves to 2.0.0. docs/releasing.md drops the podspec, lint and trunk steps, names the release branch release/X.Y.Z so it can't be confused with the tag, warns that a draft release creates no tag, and adds an SPM resolve check. The CI tag comment and PR template now describe bare tags in terms of SPM. The podspec and the cocoapods gem stay until the Objective-C demo moves to SPM. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Why
CocoaPods trunk goes read-only on Dec 2, 2026. 1.4.0 is the last version we publish there, and 2.0.0 onward ships through Swift Package Manager only. Part of 2.0.0. Don't merge until 1.4.0, the last CocoaPods release, has shipped.
What Changed
from: "2.0.0".pod lib lint/pod spec lint,pod trunk push.release/X.Y.Z, not the bare version, which made1.3.0ambiguous between branch and tag. It's a regular PR, not a draft.v) on the squash-merge commit. A draft release creates no tag; that's whyfrom: "1.3.0"didn't resolve until Nov 9.swift package resolvefinds the version.How to Test
Notes
The Objective-C demo still builds with CocoaPods: its Podfile uses
OptableSDK.podspec(:path => "../") and its lane runspod install.OptableSDK.podspecand thecocoapodsgem are deleted in a follow-up, together with that demo's move to SPM, after [BREAKING] Port OptableSDKIdentifier to Swift so SPM ships the Objective-C API #84.The README's demo build section is left to [BREAKING] Build the Swift demo with Swift Package Manager #96 and the Objective-C demo PR, so this doesn't conflict with them.
Breaking change
Requires release
🤖 Generated with Claude Code