Releases: insurely/insurely-sdk-ios-distribution
Release list
1.2.3
What's new
Distribution-only release. README correction; the InsurelySDK binary is identical to all prior 1.2.x tags.
CI access guidance scoped to where it applies
The previous Access section presented CI deploy keys as a universal requirement. They are only needed for the Swift Package Manager (remote) installation method — the local clone and manual framework methods vendor the binary into the customer's project, so their CI never reaches out to this repository at build time.
The README now reflects this:
- The top-level Access section covers only the universal requirement (every developer needs a GitHub account with read access) and links to the relevant install method for method-specific access patterns.
- The CI deploy key instructions live inside the Swift Package Manager (remote) subsection where they apply.
- The local clone and manual sections explicitly note that no CI access is required, so customers don't have to infer it.
Upgrade notes
No code changes. Customers consuming any earlier 1.2.x version can update at their convenience for the clearer documentation. The Package.swift and InsurelySDK.xcframework are unchanged.
Assets
InsurelySDK.xcframework.zip— the signed binary framework for manual integration (identical to 1.2.0–1.2.2).InsurelySDK.doccarchive.zip— Xcode documentation bundle (identical to 1.2.0–1.2.2).
1.2.2
What's new
Distribution-only release. The InsurelySDK binary is identical to 1.2.0 and 1.2.1 — this release ships only README updates.
Installation section restructured
The three installation methods — Swift Package Manager (remote), Swift Package Manager (local clone), and manual framework integration — are now presented as equal siblings rather than a primary method with alternatives. Each carries a "best when..." tag so customers can pick the right path for their environment (network-connected dev, vendored / air-gapped CI, non-SPM project) without one feeling like a second-class option.
Upgrade notes
No code changes. Customers consuming 1.2.0 or 1.2.1 can update to 1.2.2 at their convenience — there is no functional difference beyond the README content. The Package.swift and InsurelySDK.xcframework are unchanged.
Assets
InsurelySDK.xcframework.zip— the signed binary framework for manual integration (identical to 1.2.0/1.2.1).InsurelySDK.doccarchive.zip— Xcode documentation bundle (identical to 1.2.0/1.2.1).
1.2.1
What's new
Distribution-only release. The InsurelySDK binary is identical to 1.2.0 — this release ships only repo documentation and licensing updates.
Final LICENSE wording
Replaces the 1.2.0 placeholder (which was marked as pending legal review) with the final wording approved by Insurely AB legal. The license now points to the Customer Agreement as the authoritative source of terms.
Onboarding instructions in the README
A new Access section spells out who needs read access to this repository (every developer who integrates the SDK, plus any CI/CD system that resolves the package) and the recommended access patterns:
- Per-developer GitHub invites for human developers.
- Read-only deploy keys for CI machines, so personal developer credentials stay out of CI configuration.
Upgrade notes
No code changes. Customers consuming 1.2.0 can update to 1.2.1 at their convenience — there is no functional difference beyond the LICENSE wording and the README guidance. The Package.swift and InsurelySDK.xcframework are unchanged.
Assets
InsurelySDK.xcframework.zip— the signed binary framework for manual integration (identical to the 1.2.0 asset; not needed if you use Swift Package Manager).InsurelySDK.doccarchive.zip— Xcode documentation bundle (identical to the 1.2.0 asset).
1.2.0
What's new
Theme Mode API
InsurelyConfiguration now accepts an optional themeMode parameter for controlling light, dark, and system-driven theme resolution:
InsurelyConfiguration(
customerId: "...",
configName: "...",
themeMode: .system // .light, .dark, or .system
).lightor.dark— render the corresponding theme variant unconditionally..system— follow the host's color scheme viaprefers-color-scheme. The embedded WKWebView inherits the host's trait collection so CSS media queries resolve correctly.- Omitted — the embedded WebView is forced to a light color scheme. This preserves the SDK's pre-1.2.0 behavior so existing integrations see no rendering change when upgrading.
Dark mode rendering requires your BlocksConfig to include at least one ConnectedTheme. With both light and dark identifiers configured, .system will follow the device automatically. Contact your Insurely account representative if you need help setting up ConnectedTheme rows.
Removed forced light color scheme
The embedded WKWebView no longer unconditionally overrides its color scheme to .light. This unblocks dark-mode rendering when themeMode is .system or .dark. For integrations that have not set themeMode, the forced-light behavior is preserved to maintain backward compatibility.
Backward compatibility
Existing integrations that do not set themeMode see no change in behavior. The JSON wire payload sent to blocks is unchanged when themeMode is nil, and the embedded WebView still renders light regardless of the host's color scheme.
Installation
Add via Swift Package Manager:
git@github.com:insurely/insurely-sdk-ios-distribution.git
Use the Exact Version rule for 1.2.0, or Up to Next Major Version from 1.2.0 to receive non-breaking updates automatically.
Assets
InsurelySDK.xcframework.zip— the signed binary framework for manual integration (not needed if you use Swift Package Manager).InsurelySDK.doccarchive.zip— Xcode documentation bundle. Download, unzip, double-click to add to Xcode's documentation browser.