[jao-tawk]

Whats new

Bump the version from 6.9 to 7.1. Run the Full test suite and pin 7.1 wordpress image to test it properly 100% in latest version of wordpress.

[greptile-apps]

Confidence Score: 4/5

[Low impact] The changes affect published plugin and compatibility labels only.

Fix the upgrade path before merging so the release does not clear saved Secure Mode keys.

Findings

1.  Updating clears saved keys ▶
2.  Tests can check another version ▶

Fix with agent prompt

### Issue 1
tawkto/tawkto.php:9
Bumping the plugin version makes sites with a saved `tawkto-version` of `0.9.3` run old upgrades again. `TawkToUpgradeManager::start()` checks each upgrade against the new version, but not the saved version. This reruns `TawkToUpgradeVersion090::upgrade()`, which replaces the saved `js_api_key` with an empty string. Sites that configured Secure Mode lose their key after updating.

Skip upgrades that already ran and save the current plugin version when finished.

### Issue 2
tawkto/readme.txt:undefined-6
The PR declares WordPress 7.1 support and says tests should be pinned to that version, but the test setup still uses `wordpress:latest` and runs `wp core update`. Repeat runs can therefore check a different WordPress version without any repository change. Pin both the image and the setup script to 7.1 so tests consistently check the release named here.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Updates the plugin release to 0.9.4 and declares WordPress 7.1 compatibility.

• The plugin’s release labels move to 0.9.4, and its tested WordPress version moves to 7.1.

_{Reviews (5) · Last reviewed commit: "chore: update lock file" · Reviewed by Greptile}

[greptile-apps]

Tests can check another version

The PR declares WordPress 7.1 support and says tests should be pinned to that version, but the test setup still uses wordpress:latest and runs wp core update. Repeat runs can therefore check a different WordPress version without any repository change. Pin both the image and the setup script to 7.1 so tests consistently check the release named here.

Prompt To Fix With AI

This is a comment left during a code review.
Path: tawkto/readme.txt
Line: 6

Comment:
**Tests can check another version**

The PR declares WordPress 7.1 support and says tests should be pinned to that version, but the test setup still uses `wordpress:latest` and runs `wp core update`. Repeat runs can therefore check a different WordPress version without any repository change. Pin both the image and the setup script to 7.1 so tests consistently check the release named here.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[greptile-apps]

Updating clears saved keys

Bumping the plugin version makes sites with a saved tawkto-version of 0.9.3 run old upgrades again. TawkToUpgradeManager::start() checks each upgrade against the new version, but not the saved version. This reruns TawkToUpgradeVersion090::upgrade(), which replaces the saved js_api_key with an empty string. Sites that configured Secure Mode lose their key after updating.

Skip upgrades that already ran and save the current plugin version when finished.

Prompt To Fix With AI

This is a comment left during a code review.
Path: tawkto/tawkto.php
Line: 9

Comment:
**Updating clears saved keys**

Bumping the plugin version makes sites with a saved `tawkto-version` of `0.9.3` run old upgrades again. `TawkToUpgradeManager::start()` checks each upgrade against the new version, but not the saved version. This reruns `TawkToUpgradeVersion090::upgrade()`, which replaces the saved `js_api_key` with an empty string. Sites that configured Secure Mode lose their key after updating.

Skip upgrades that already ran and save the current plugin version when finished.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.