Prepare the 0.7.2 release

CHANGELOG.md

@@ -6,6 +6,8 @@ bump may contain breaking changes, and each one is listed below.
 
 ## [Unreleased]
 
+## [0.7.2] - 2026-09-13
+
 ### Fixed
 
 - A VoIP push that arrives before the host has called
@@ -25,6 +27,10 @@ bump may contain breaking changes, and each one is listed below.
   worker; the stack is now initialized and the thread registered before
   `pjsua_create()`, and the teardown balances that initialization.
 
+Physical-device verification of 0.7.2 is pending; every fix in it sits on the
+push and registration path, which the simulator suite cannot exercise against a
+real PBX.
+
 ## [0.7.1] - 2026-09-08
 
 ### Fixed

CallWaveKit.podspec

@@ -1,6 +1,6 @@
 Pod::Spec.new do |spec|
   spec.name = 'CallWaveKit'
-  spec.version = '0.7.1'
+  spec.version = '0.7.2'
   spec.summary = 'Incoming SIP SDK for iOS intercoms.'
   spec.description = <<-DESC
     CallWaveKit owns a PJSUA runtime, SIP registration, incoming audio calls,

FIELD-TESTING.md

@@ -9,6 +9,20 @@ done by hand, on a device, against an intercom.
 Run it before tagging a release, and after any change to the answer path, the
 push path, the audio session or the registration lifecycle.
 
+## 0.7.2 run record
+
+Physical-device pass: **not run** at release time. 0.7.2 changes the push and
+registration path, which this file names as the trigger for a new pass, so the
+matrix below is owed for it. What the release specifically wants confirmed:
+
+- scenario 1 and 11, on a build whose credentials arrive with the push — the log
+  must carry `no SIP account yet; waiting for -loginWithConfiguration:` and no
+  `No configuration` error;
+- the PBX log for a host-owned CallKit integration: one `REGISTER` per incoming
+  push, not two;
+- scenario 7, to confirm that ten calls in a row still register and answer after
+  the PJLIB initialization change.
+
 ## 0.7.1 run record
 
 Physical-device pass: **not run**. The release is authorized to deliver the

README.md

@@ -36,13 +36,13 @@ not grant or transfer a proprietary PJSIP licence.
 ### Swift Package Manager
 
 In Xcode: **File → Add Package Dependencies**, enter
-`https://github.com/PetrShtuka/CallWaveKit.git`, pick version `0.7.1` or later,
+`https://github.com/PetrShtuka/CallWaveKit.git`, pick version `0.7.2` or later,
 and add the `CallWaveKit` product to your application target.
 
 Or in a `Package.swift`:
 
 ```swift
-.package(url: "https://github.com/PetrShtuka/CallWaveKit.git", from: "0.7.1")
+.package(url: "https://github.com/PetrShtuka/CallWaveKit.git", from: "0.7.2")
 ```
 
 The product vends two modules: `CallWaveKit` (the Objective-C API) and
@@ -63,7 +63,7 @@ To track the repository directly instead of the published pod — an unreleased
 fix, say — point at the tag:
 
 ```ruby
-pod 'CallWaveKit', git: 'https://github.com/PetrShtuka/CallWaveKit.git', tag: '0.7.1'
+pod 'CallWaveKit', git: 'https://github.com/PetrShtuka/CallWaveKit.git', tag: '0.7.2'
 ```
 
 ## Host application settings
@@ -215,7 +215,7 @@ SwiftPM releases use an immutable binary asset so package consumers do not
 download the 21 MB framework through Git history. To package a rebuilt binary:
 
 ```sh
-./Scripts/package-pjsip-release.sh 0.7.1
+./Scripts/package-pjsip-release.sh 0.7.2
 ```
 
 The script prints the archive checksum and the `.binaryTarget(url:checksum:)`

RELEASING.md

@@ -68,7 +68,7 @@ CocoaPods fail with a version mismatch, because `spec.source` resolves
 ### 3. Tag
 
 ```sh
-RELEASE_VERSION=0.7.1
+RELEASE_VERSION=0.7.2
 git checkout main
 git pull
 git tag -a "$RELEASE_VERSION" -m "CallWaveKit $RELEASE_VERSION"

Scripts/package-pjsip-release.sh

@@ -6,8 +6,8 @@
 # checkout pays for it, so a tagged release should attach the zip instead and
 # Package.swift should point at that URL:
 #
-#   ./Scripts/package-pjsip-release.sh 0.7.1
-#   gh release upload 0.7.1 build/PJSIP.xcframework.zip
+#   ./Scripts/package-pjsip-release.sh 0.7.2
+#   gh release upload 0.7.2 build/PJSIP.xcframework.zip
 #
 # Then replace the `path:` binary target in Package.swift with the printed
 # `url:`/`checksum:` pair. Keep the local `path:` variant on a branch you