Skip to content

Latest commit

 

History

History
33 lines (18 loc) · 2.67 KB

File metadata and controls

33 lines (18 loc) · 2.67 KB

CocoaPods distribution for ContentstackUtils

This notice applies to developers who integrate ContentstackUtils using CocoaPods (ContentstackUtils pod).

What this package is

ContentstackUtils is a companion library for the Contentstack Swift SDK. It provides utilities (for example JSON RTE rendering and embedded items) for use alongside the Swift Content Delivery API (CDA) client. It is not a replacement for the core CDA SDK—you still use the Swift SDK for stack, queries, and delivery.

What we recommend for new work

For new projects and new integrations, we recommend adding ContentstackUtils with Swift Package Manager (SPM) from this repository, and using the Swift SDK via SPM as well. That keeps your dependency graph aligned with current tooling and our primary distribution path.

Version alignment: Use ContentstackUtils versions that match the guidance in this repository’s README (keep Utils in step with the Swift SDK version you use).

We are deprecating CocoaPods as the recommended way to add ContentstackUtils for new work. CocoaPods remains part of the broader ecosystem, but our product direction favors SPM for Apple platforms. For background on how the CocoaPods ecosystem is evolving, see CocoaPods Specs Repo.

If you already use CocoaPods

Existing apps that already depend on the ContentstackUtils pod can continue to ship as they do today. You are not required to migrate on a fixed deadline to keep using what you have. When you are ready to standardize on SPM or refresh dependencies, plan a migration at your own pace.

Maintenance and features

We continue to maintain ContentstackUtils for supported integration paths. New feature work and documentation will emphasize SPM and the Swift SDK. CocoaPods-based setups may receive necessary maintenance but are not our focus for new capabilities.

Support

Questions or help with your integration: support@contentstack.io.

See also the Important section at the top of the README.