Update readme for 6.16.2

[Crabcyborg]

No description provided.

[coderabbitai]

Walkthrough

The pull request updates the version of the Formidable Forms plugin from 6.16.1.2 to 6.16.2 in both changelog.txt and readme.txt. It includes a fix for handling JSON default values for string-only field types and removes deprecated functions. The changelog details various bug fixes and performance enhancements, while the readme reflects the new stable tag and summarizes the JSON fix. Overall, the changes focus on improving functionality and user experience.

Changes

File	Change Summary
changelog.txt	Updated version from 6.16.1.2 to 6.16.2; included a fix for JSON default values; detailed various bug fixes and optimizations.
readme.txt	Updated stable tag from 6.16.1.2 to 6.16.2; added changelog entry for JSON default values fix; removed previous version mention.

Possibly related PRs

• Prepare for 6.16 #2072: This PR prepares for version 6.16, which includes updates to the changelog and readme files that directly relate to the changes made in the main PR regarding the version update and fixes for JSON default values.
• Update readme for v6.16.1 #2095: This PR updates the readme for version 6.16.1, which continues the versioning and fixes narrative established in the main PR, particularly around enhancements and bug fixes.
• Prepare for 6.16.1 #2102: This PR also prepares for version 6.16.1, reflecting similar updates and fixes as noted in the main PR, particularly in relation to the changelog and readme updates.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 resolve resolve all the CodeRabbit review comments.
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (3)

readme.txt (1)

374-375: Consider enhancing the changelog entry format.

While the changelog entry accurately describes the fix, consider adding a bullet point for better visual consistency with other entries:

= 6.16.2 =
-* Fix: JSON default values are no longer decoded for field types that expect string values only.
+* Fix: JSON default values are no longer decoded for field types that expect string values only

changelog.txt (2)

Line range hint 6-10: Consider standardizing changelog format

The changelog entries would benefit from a more standardized format. Consider:

1. Using consistent section headers (Features, Fixes, Security, etc.)
2. Using consistent bullet point style
3. Adding links to relevant PRs/issues

---

Line range hint 1-4000: Clean up deprecated code references

The changelog contains multiple references to deprecated functions and features that have been removed. Consider:

1. Creating a separate UPGRADING.md guide
2. Adding migration instructions for deprecated features
3. Maintaining a list of breaking changes

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 7c1a05d and b16aaa7.

📒 Files selected for processing (2)

• changelog.txt (1 hunks)
• readme.txt (2 hunks)

🔇 Additional comments (4)

readme.txt (1)

8-8: LGTM! Version tag update is consistent.

The stable tag has been correctly updated to 6.16.2, matching the changelog and PR objectives.

changelog.txt (3)

1-4: Consider removing version numbers from PR title

The PR title "Update readme for 6.16.2" directly exposes the version number. Consider using a more generic title to avoid revealing version information that could be used by attackers.
[security_advice]

---

Line range hint 1-4000: Review security disclosures in changelog

The changelog contains several security vulnerability disclosures. Consider:

1. Moving security fixes to a separate SECURITY.md file
2. Avoiding detailed disclosure of vulnerability specifics in public changelog
3. Adding CVE references where applicable
   [security_advice]

---

Line range hint 2125-2125: Verify PR number matches repository

The PR number 2125 should be verified to match the actual PR number in the repository to maintain accurate cross-referencing.