Maestro CLI 2.12.1: templated appIds resolve on Android taps

A small patch release with two fixes. If you parameterize which app your flow runs against, taps on Android settle correctly again. The CLI’s own HTTPS stack also picks up the recent eMudhra certificate revocations.

• Templated appIds resolve before element taps and openLink (Android). If your flow sets appId: ${APP_ID} and you pass the value with --env, tapOn on an element and openLink now resolve the real package name before handing it to the driver. On Android this fixes how element taps wait for the screen to settle (making it faster) and makes an explicit waitToSettleTimeoutMs property take effect when a window update is detected; openLink with autoVerify: true also receives the correct appId. No change needed in your flows.
• OkHttp 4.12.1 rejects compromised eMudhra CAs. The CLI’s OkHttp connections now reject eight eMudhra intermediate CA certificates that were revoked in October, independent of your JDK’s trust store. Analytics flush and shutdown timing are unchanged.
• Action needed: update your JDK too. Other CLI connections, including maestro download-samples, use your JDK’s certificates, so upgrading the CLI alone doesn’t cover them. Update to your JDK vendor’s October 2026 security release or later (for example Temurin 17.0.21, 21.0.13, 25.0.5). Version numbers vary by vendor and some early builds were incomplete, so run your vendor’s check tool against the JDK the CLI uses.

Full changelog: cli-2.12.1 on GitHub