cocoapods-publishing-workflow

Publishing to trunk automates distributing your iOS/macOS library through CocoaPods. Register for trunk once, validate your podspec locally and remotely, tag your version in git, then push to trunk. The Skill handles all registration, validation, tagging, and publishing steps end-to-end.

Trunk registration is a one-time setup that authorizes your account to publish CocoaPods libraries. Once registered, you can publish multiple versions of your podspec without re-registering.

Podspec validation checks your library configuration locally and remotely against CocoaPods standards. Local validation catches syntax and structure errors in your podspec file; remote validation verifies your library meets trunk requirements before publishing.

Yes. The publishing workflow automates version tagging in git and pushing to trunk as coordinated steps. After validating your podspec, tag your release version and push to trunk in a single automated sequence.

Validation failures indicate missing or incorrect podspec fields, incompatible dependencies, or platform mismatches. The Skill identifies which validation step failed—local or remote—so you can fix your podspec configuration before attempting to publish again.

The publishing workflow handles CocoaPods trunk operations through automation, but familiarity with Ruby, podspec syntax, and basic git commands (tagging, pushing) helps. The Skill guides you through each step so you understand what each stage validates and performs.