[JakubMrozek]

Summary

Release prep for KontextKit 0.0.5 — a license-compliance fix for the bundled IAB OMSDK xcframework.

IAB Tech Lab OM License v1.1 Section 4(a) requires Object-form redistributions of the OMSDK to include a copy of the License alongside the artifact. KontextKit ships Frameworks/OMSDK_Kontextso.xcframework via s.vendored_frameworks in the podspec, but the xcframework binary does not embed any LICENSE file internally — and the 0.0.4 pod only shipped KontextKit's own LICENSE (Apache-2.0). Downstream consumers therefore received the binary without the license text it ships under.

Changes

• Frameworks/OMLICENSE (new) — OM License v1.1 text, unmodified from the IAB Tech Lab distribution, placed next to the xcframework.
• KontextKit.podspec:
  • s.version bumped 0.0.4 → 0.0.5.
  • s.preserve_paths = "Frameworks/OMLICENSE" keeps the file in the published pod (preserve_paths is the right knob for documentation-style files that shouldn't be compiled or processed).
  • Description expanded to clarify the dual-licensing: Apache-2.0 for KontextKit's own Swift sources, OM License v1.1 for the bundled xcframework.
• CHANGELOG.md — new 0.0.5 entry at the top.

Scope of this release

• License only. The xcframework binary is unchanged — still IAB OMSDK 1.6.4. No source-level changes in Sources/.
• SPM consumers see the file naturally via the git checkout; Package.swift resolves the whole tree, so no Package.swift change is needed.

Cross-platform context

Mirrors the equivalent fix for Android in kontextso/kontextkit-android#9, shipped in 0.0.6 (added omsdk-android/LICENSE next to the redistributed AAR). Same OM License v1.1, same Section 4(a) obligation.

Verification

• pod lib lint KontextKit.podspec --allow-warnings --use-libraries passes for KontextKit (0.0.5) — same check pod trunk push runs at release time.
• pod spec lint --quick passes.
• Build kontextkit-ios on iOS Simulator (no source-level changes; should be unaffected, but worth a smoke before tagging).
• After release, verify a fresh pod install of KontextKit:0.0.5 in a consumer project creates Pods/KontextKit/Frameworks/OMLICENSE on disk.

Release plan

Per the standard kontextkit-ios flow (see RELEASING.md):

1. Merge this PR to main.
2. Tag 0.0.5 annotated; push the tag.
3. pod trunk push KontextKit.podspec --allow-warnings --use-libraries from main.
4. Verify on CocoaPods + GitHub release page.

🤖 Generated with Claude Code