supported version bump to 6.9; version bump to 0.9.3

[eug-L]

Summary by CodeRabbit

• Chores
  • Bumped package version to 0.9.3 across all manifests and configuration files.
  • Updated compatibility information to support version 6.9.
  • Updated changelog documentation for the 0.9.3 release.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR bumps the package version from 0.9.2 to 0.9.3 across multiple configuration and plugin files. The readme also updates the "Tested up to" version from 6.8 to 6.9 and includes a corresponding changelog entry.

Changes

Cohort / File(s)	Change Summary
Version bumps in dependency managers composer.json, package.json	Version incremented from 0.9.2 to 0.9.3
WordPress plugin version and documentation tawkto/tawkto.php, tawkto/readme.txt, tawkto/templates/widget.php	Plugin version bumped to 0.9.3; readme updated with "Tested up to" version 6.9 and new changelog entry for 0.9.3

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• supported version bump to 6.8; version bump to 0.9.2 #41: Both PRs make matching edits to version fields across the same files (composer.json, package.json, plugin header/readme/widget comments), incrementing the release version.

Suggested reviewers

• GeekOfAges

Poem

🐰 Hop skip and a bound, the versions now round!
From 0.9.2 to 0.9.3, a tag so fine!
The changelog's penned, the testing's been sent,
A release so neat, oh how divine! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the two main changes in the PR: bumping the supported WordPress version to 6.9 and bumping the package version to 0.9.3.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d612385 and ac61e7c.

⛔ Files ignored due to path filters (2)

• composer.lock is excluded by !**/*.lock
• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (5)

• composer.json
• package.json
• tawkto/readme.txt
• tawkto/tawkto.php
• tawkto/templates/widget.php

🔇 Additional comments (6)

tawkto/readme.txt (2)

6-7: LGTM!

Version metadata correctly updated: "Tested up to" bumped to 6.9 and "Stable tag" updated to 0.9.3, consistent with the PR objectives.

---

74-76: LGTM!

Changelog entry follows the established pattern used in previous version bumps (e.g., 0.9.2).

package.json (1)

3-3: LGTM!

Version correctly bumped to 0.9.3, consistent with the coordinated version update across all project files.

tawkto/templates/widget.php (1)

11-11: LGTM!

Version markers in the HTML comments correctly updated to 0.9.3. This helps identify the plugin version in rendered output for debugging purposes.

Also applies to: 27-27

tawkto/tawkto.php (1)

9-9: LGTM!

Plugin header version correctly updated to 0.9.3. This is the authoritative version declaration used by WordPress to display plugin information in the admin dashboard.

composer.json (1)

6-6: LGTM!

Version correctly bumped to 0.9.3. All five files in this PR now have consistent version numbering.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}