supported version bump to 6.8; version bump to 0.9.2

[eug-L]

Summary by CodeRabbit

• Chores
  • Updated the project version from 0.9.1 to 0.9.2.
  • Refreshed metadata and compatibility information to support up to version 6.8.

[coderabbitai]

Walkthrough

The pull request updates the project’s version number from 0.9.1 to 0.9.2 across several files. In addition to version bumps in configuration and plugin header comments, the plugin’s readme file also reflects an updated "Tested up to" version (6.7 to 6.8) and includes a corresponding changelog entry.

Changes

Files	Summary
composer.json, package.json, tawkto/tawkto.php, tawkto/.../widget.php	Updated version fields/comments from 0.9.1 to 0.9.2
tawkto/readme.txt	Updated version details: Stable tag changed from 0.9.1 to 0.9.2, "Tested up to" updated from 6.7 to 6.8, changelog added

Poem

I hopped through lines of code today,
Bumping versions in a careful, steady sway.
From 0.9.1 to 0.9.2, the numbers dance and gleam,
With updated tags and tested themes.
A carrot in paw, I cheer the change unseen!
Codes and tummies full – a coder rabbit's dream!

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1d7d672 and 2b48329.

⛔ 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 (1 hunks)
• package.json (1 hunks)
• tawkto/readme.txt (2 hunks)
• tawkto/tawkto.php (1 hunks)
• tawkto/templates/widget.php (2 hunks)

🔇 Additional comments (7)

package.json (1)

3-3: Version Field Update in package.json
The package version has been updated to "0.9.2", which correctly reflects the new release. Please verify that any integrations or automated tools consuming this version continue to operate as expected.

tawkto/tawkto.php (1)

9-9: Plugin Header Version Bump
The version number in the plugin header has been updated to 0.9.2, ensuring consistency with the release notes and other files. No further code changes are needed here.

composer.json (1)

6-6: Composer Version Update
The "version" property in composer.json is updated to "0.9.2". This maintains coherence with the overall versioning strategy across the project.

tawkto/templates/widget.php (2)

11-11: Widget Script Start Comment Update
The starting HTML comment now displays <!--Start of Tawk.to Script (0.9.2)-->, which accurately indicates the current version of the embedded script.

---

27-27: Widget Script End Comment Update
The ending HTML comment has been updated to <!--End of Tawk.to Script (0.9.2)-->, reflecting the correct release version.

tawkto/readme.txt (2)

6-7: Metadata Version and Compatibility Update
The "Tested up to" field is updated to 6.8 and the "Stable tag" is now 0.9.2. This clearly communicates the compatibility with newer WordPress versions and reflects the new release status.

---

74-76: Changelog Entry Update
The changelog now includes an entry for version 0.9.2, with a note stating "* Supported version bump to 6.8*". This update improves documentation clarity for users.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.