cordova-khipu 2.11.0 → 2.11.2

package/README.md

@@ -24,8 +24,9 @@ Cordova plugin for Khipu
 | `cordova` (CLI) | 13.0.0 | 13.0.0 |
 | `cordova-ios` | 7.0.0 | 7.1.1 and 8.1.1 |
 | `cordova-android` | 13.0.0 | 13.0.0, 14.0.0 and 15.1.0 |
-| iOS | 13.0 | |
-| Node | `^20.17.0 \|\| >=22.9.0` | 20.19.4 |
+| iOS | 13.0, or 15.0 with Xcode 27 | |
+| Node | `^20.17.0 \|\| >=22.9.0` | 22.23.2, and 20.17.0 for the hooks' unit tests |
+| Xcode | 26 | 26.6, and 27.0 by hand (see [Xcode 27](#xcode-27-needs-a-deployment-target-of-150)) |
 
 Of this table, only `cordova-ios` and `cordova-android` are declared in `plugin.xml`'s
 `<engines>`. Mind what that does: if the installed platform does not meet the minimum,
@@ -37,9 +38,11 @@ with exit code 0 (verified in `checkEngines()` and the `catch` around it,
 minimum sees a green install, the plugin gets listed in their `package.json`, nothing
 native gets installed, and they only discover the problem at runtime with
 `window.Khipu === undefined`. What protects the merchant is reading that warning, not an
-error Cordova never throws. The other three rows (`cordova` CLI, iOS, Node) are tested
-and recommended compatibility, not an automatic barrier — Cordova's engine check does not
-even recognize a `node` type, and the plugin's `package.json` does not declare `engines`.
+error Cordova never throws. The other four rows (`cordova` CLI, iOS, Node, Xcode) are
+tested and recommended compatibility, not an automatic barrier — Cordova's engine check
+does not even recognize a `node` type, and the plugin's `package.json` does not declare
+`engines`. Xcode's minimum is App Store Connect's: it has required Xcode 26 for uploads
+since April 28, 2026.
 
 ## Installation
 
@@ -95,7 +98,8 @@ in `config.xml` **before** adding the platform:
 The other three cases are for `cordova-ios` 8:
 
 1. **If iOS 13 is enough for you, do not declare it.** The default is already 13.0 and
-   the plugin stays on SPM, without touching CocoaPods.
+   the plugin stays on SPM, without touching CocoaPods. This holds on Xcode 26 only: on
+   Xcode 27, 13.0 no longer builds, see [below](#xcode-27-needs-a-deployment-target-of-150).
 2. **If you declare it with any value, including 13.0, you will need CocoaPods.** The
    plugin still ships a `<podspec>` — the `cordova-ios` 7 path needs it — so cordova
    creates an empty `Podfile` when installing the plugin regardless. When `config.xml`
@@ -106,6 +110,38 @@ The other three cases are for `cordova-ios` 8:
    avoid: it is the consequence of the plugin supporting both managers from a single
    `plugin.xml`.
 
+### Xcode 27 needs a deployment target of 15.0
+
+Xcode 27 turns a deployment target below iOS 15.0 into a build error, not a warning:
+
+```
+The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 13.0, but the
+range of supported deployment target versions is 15.0 to 27.0.x.
+```
+
+On Xcode 26, 13.0 still builds and nothing above changes. On Xcode 27:
+
+- **On `cordova-ios` 8, declare 15.0**, before adding the platform:
+
+  ```xml
+      <platform name="ios">
+          <preference name="deployment-target" value="15.0" />
+      </platform>
+  ```
+
+  That is case 3 above, so you will need CocoaPods installed, but Khipu's SDK still
+  arrives through SPM. Nothing about the plugin needs changing: Xcode raises the SDK's
+  Swift packages to 15.0 on its own.
+- **`cordova-ios` 7 does not build on Xcode 27, whatever you declare.** Two things stay
+  below 15.0 and the preference reaches neither: `CordovaLib`, which `cordova-ios` 7 ships
+  at 11.0, and the pods of Khipu's SDK, which declare 12.0. Keep building with Xcode 26, or
+  move to `cordova-ios` 8.
+
+This was measured with Xcode 27.0 (build 27A266a) on the [example app](#example-app),
+with `cordova build ios --emulator`: `cordova-ios` 8.1.1 fails at 13.0 and builds at 15.0,
+and `cordova-ios` 7.1.1 still fails at 15.0 on exactly those two. CI builds with Xcode
+26.6, so it does not cover Xcode 27 yet.
+
 ### Swift version
 
 The plugin configures `SWIFT_VERSION` on its own when needed. If you need a different

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cordova-khipu",
-  "version": "2.11.0",
+  "version": "2.11.2",
   "description": "Khipu Cordova Plugin",
   "types": "types/index.d.ts",
   "cordova": {
@@ -40,7 +40,7 @@
     "LICENSE"
   ],
   "scripts": {
-    "test": "node --test tests/scripts/ tests/js/",
+    "test": "node --test tests/scripts/*.test.js tests/js/*.test.js",
     "verify": "npm test && npm run verify:versions && npm run verify:keys && npm run verify:ios && npm run verify:android",
     "verify:versions": "node scripts/check-native-versions.js",
     "verify:keys": "node scripts/check-option-keys.js",
@@ -51,11 +51,11 @@
     "prepare": "husky"
   },
   "devDependencies": {
-    "@commitlint/config-conventional": "^19.6.0",
-    "@release-it/conventional-changelog": "^9.0.3",
-    "commitlint": "^19.6.1",
+    "@commitlint/config-conventional": "^21.2.3",
+    "@release-it/conventional-changelog": "^12.0.2",
+    "commitlint": "^21.2.3",
     "husky": "^9.1.7",
-    "release-it": "^17.10.0"
+    "release-it": "^21.1.0"
   },
   "commitlint": {
     "extends": [
@@ -78,7 +78,7 @@
     },
     "plugins": {
       "@release-it/conventional-changelog": {
-        "preset": "angular",
+        "preset": "conventionalcommits",
         "infile": "CHANGELOG.md"
       }
     },

package/plugin.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
-<plugin id="cordova-khipu" version="2.11.0" xmlns="http://apache.org/cordova/ns/plugins/1.0" xmlns:android="http://schemas.android.com/apk/res/android">
+<plugin id="cordova-khipu" version="2.11.2" xmlns="http://apache.org/cordova/ns/plugins/1.0" xmlns:android="http://schemas.android.com/apk/res/android">
   <name>Cordova Khipu</name>
   <engines>
     <engine name="cordova-ios" version=">=7.0.0"/>

package/scripts/ios-destination.js

@@ -1,8 +1,8 @@
 #!/usr/bin/env node
 // Prints an xcodebuild -destination for an iOS simulator that actually exists here.
 //
-// `-destination 'platform=iOS Simulator,name=iPhone 16'` is what CI uses, and it works there,
-// but it resolves to OS:latest — so on a machine whose newest installed runtime has no iPhone 16
+// `-destination 'platform=iOS Simulator,name=iPhone 17'` is what CI uses, and it works there,
+// but it resolves to OS:latest — so on a machine whose newest installed runtime has no iPhone 17
 // it fails with "Unable to find a device matching the provided destination specifier", and the
 // whole verify chain stops before it reaches the Android suite. Pinning a runtime instead just
 // moves the problem to whoever does not have that one.

package/src/android/khipu.gradle

@@ -8,5 +8,5 @@ repositories {
 }
 
 dependencies {
-    implementation 'com.khipu:khipu-client-android:2.28.5'
+    implementation 'com.khipu:khipu-client-android:2.28.6'
 }

package/tests/android/build.gradle

@@ -38,7 +38,7 @@ android {
 }
 
 dependencies {
-    implementation 'com.khipu:khipu-client-android:2.28.5'
+    implementation 'com.khipu:khipu-client-android:2.28.6'
 
     testImplementation 'junit:junit:4.13.2'
     // org.json inside android.jar is a set of stubs whose every method throws

package/tests/android/src/test/java/com/khipu/cordova/SdkContractTest.java

@@ -19,7 +19,7 @@ import java.util.Arrays;
  * Android framework, every mapper test would fail at once with a confusing error. This
  * test fails first, with an obvious one.
  *
- * The second is part of the reason src/android/khipu.gradle says 2.28.5 and not 2.27.0.
+ * The second is part of the reason src/android/khipu.gradle says 2.28.6 and not 2.27.0.
  * Protocol 1.0.59 has fourteen FailureReasonType constants and no USER_DISCONNECTED; its
  * forValue() throws IOException on any value it does not know, and the SDK's
  * OPERATION_FAILURE listener calls the converter with no try/catch on socket.io's