Prepare for 6.26.1

[Crabcyborg]

No description provided.

[coderabbitai]

Walkthrough

The PR bumps the plugin version from 6.26 to 6.26.1 across multiple metadata files and adds corresponding changelog entries documenting performance, UI, validation, and breaking changes implemented in this release.

Changes

Cohort / File(s)	Summary
Version metadata updates changelog.txt, readme.txt, formidable.php	Version number updated from 6.26 to 6.26.1; new 6.26.1 changelog entries added documenting license check autoload, SVG icon updates, field step validation fixes, Bootstrap dropdown initialization, and removal of onblur blur event.
Plugin version declaration classes/helpers/FrmAppHelper.php	Public static property $plug_version updated from '6.26' to '6.26.1'.
Documentation update classes/helpers/FrmStylesHelper.php	@since tag in docblock updated from x.x to 6.26.1.
Translation catalog languages/formidable.pot	POT version header updated from 6.26 to 6.26.1; POT-Creation-Date timestamp updated; source reference line mappings adjusted to reflect current file line numbers.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• All changes are straightforward version number and metadata updates with no functional logic modifications.
• Translation file updates are automated reference adjustments with no semantic content changes.

Possibly related PRs

• Strategy11/formidable-forms#2643: Direct predecessor that bumps FrmAppHelper::$plug_version to 6.26, upon which this patch release builds.
• Strategy11/formidable-forms#2490: Follows the same version-bump pattern, updating plugin version across metadata and code files.
• Strategy11/formidable-forms#2308: Similar version bump PR that also updates @since metadata alongside version declarations.

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided by the author, making it impossible to assess whether the description relates to the changeset.	Consider adding a description that explains the purpose of the 6.26.1 release, such as highlighting key features, fixes, or breaking changes mentioned in the changelog.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Prepare for 6.26.1' is specific and clearly related to the main changeset, which involves updating the plugin version from 6.26 to 6.26.1 across multiple files and changelog entries.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch prepare_for_6.26.1

---

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.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

changelog.txt (1)

2-7: 6.26.1 changelog entry looks consistent; optional copy tweak for the step-setting fix

The new 6.26.1 section reads well and is consistent with prior entries. If you touch this again, you might consider rephrasing the step-setting bullet to describe the current fixed behavior (e.g., that "any" is now accepted again where appropriate) rather than only restating what changed in the last release. Not required, just a clarity polish.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 67005e3 and 82ba23f.

⛔ Files ignored due to path filters (1)

• js/formidable.min.js is excluded by !**/*.min.js, !**/*.min.js

📒 Files selected for processing (6)

• changelog.txt (1 hunks)
• classes/helpers/FrmAppHelper.php (1 hunks)
• classes/helpers/FrmStylesHelper.php (1 hunks)
• formidable.php (1 hunks)
• languages/formidable.pot (13 hunks)
• readme.txt (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)

• GitHub Check: Cypress
• GitHub Check: PHP 8 tests in WP trunk
• GitHub Check: PHP 7.4 tests in WP trunk
• GitHub Check: Cypress
• GitHub Check: PHP 7.4 tests in WP trunk
• GitHub Check: PHP 8 tests in WP trunk

🔇 Additional comments (7)

formidable.php (1)

5-5: LGTM! Version bump looks correct.

The plugin header version has been properly updated to 6.26.1, consistent with the version updates in other files.

classes/helpers/FrmStylesHelper.php (1)

509-509: LGTM! Documentation properly updated.

The @since tag has been correctly updated from the placeholder x.x to 6.26.1, properly documenting when this method was introduced.

classes/helpers/FrmAppHelper.php (1)

32-32: LGTM! Version constant properly updated.

The plugin version constant has been correctly updated to 6.26.1, maintaining consistency across all version references in the codebase.

languages/formidable.pot (2)

5-12: Header version and POT creation date look correct

Project-Id-Version now matches Formidable Forms 6.26.1, and POT-Creation-Date reflects a recent regeneration. This is consistent with the release prep and needs no changes.

---

188-9312: Reference line updates are consistent with regenerated POT

All other changes are updated source references (PHP/JS line numbers, additional js/src/admin/admin.js references, etc.) with unchanged msgid content. This is expected from regenerating the POT for 6.26.1 and does not introduce any functional or i18n issues.

readme.txt (2)

8-8: Stable tag bump to 6.26.1 looks correct

The stable tag now matches the documented 6.26.1 release. Just make sure the plugin header and any internal version constants (e.g., FrmAppHelper::$plug_version) are also set to 6.26.1 in this release.

---

375-381: Readme changelog for 6.26.1 is aligned with main changelog

The new 6.26.1 changelog block here matches changelog.txt and clearly calls out the performance, SVG, step-setting, dropdown, and breaking blur-logic changes. No further changes needed from a docs perspective.