Release v1.31.1 - #1228
Conversation
[Backport] Release v1.31.0
…y ajax These are all set to: '-5' means that the user does not have permission to view this information for this post
…ers-and-callbacks' into william/tweak/some-request-handlers-and-callbacks
This change includes a link to the privacy policy in the newsletter subscription form, ensuring users are informed about email consent. [PRO-275]
[PRO-275]
Changed justify-content from 'start' to 'flex-start' for better support across browsers. [PRO-275]
…est-handlers-and-callbacks Use a specifically named ajax request for frontend highlighter
…vacy-policy-statementlink-to-newletter-forms-in-the Add privacy policy statement link to newsletter forms
…slations_september-04-2025-18-06-20958115 PTC accessibility-checker (1985): Automatic Translations September 04, 2025 18:06:20958115
|
Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the WalkthroughVersion bump from 1.31.0 to 1.31.1 across plugin header/constant, package.json, and readme stable tag. No logic, behavior, or control-flow changes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Pull Request Overview
This PR updates the Accessibility Checker plugin from version 1.31.0 to 1.31.1, representing a patch release in the plugin versioning. The changes consist of standard version number updates across the plugin's core files to maintain consistency between the plugin header, package configuration, and WordPress plugin directory listing.
- Updates version numbers from 1.31.0 to 1.31.1 across all relevant files
- Maintains consistency between plugin metadata and package configuration
- Follows semantic versioning conventions for a patch release
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| readme.txt | Updates stable tag version for WordPress plugin directory |
| package.json | Updates npm package version for build tooling |
| accessibility-checker.php | Updates plugin header version and EDAC_VERSION constant |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary of Changes
Hello @pattonwebz, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request primarily serves to increment the version number of the Accessibility Checker plugin to 1.31.1. This change prepares the codebase for a new release, ensuring all internal and external version indicators are aligned with the upcoming stable tag.
Highlights
- Version Increment: The plugin's version number has been consistently updated from 1.31.0 to 1.31.1 across all relevant configuration and source files.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Code Review
This pull request correctly bumps the version number to 1.31.1 in accessibility-checker.php, package.json, and readme.txt. The changes are consistent for a release. However, the changelog in readme.txt has not been updated to reflect the changes in this new version, which is an important step for users. I've added a comment regarding this.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (3)
accessibility-checker.php(2 hunks)package.json(1 hunks)readme.txt(1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
readme.txt
📄 CodeRabbit inference engine (.github/copilot-instructions.md)
Update readme.txt for each release with relevant changes
Files:
readme.txt
**/*.php
📄 CodeRabbit inference engine (.github/copilot-instructions.md)
**/*.php: Follow WordPress Coding Standards (WPCS) in all PHP files
Class names use CamelCase (ClassNameConvention) for new classes
Use edac_ prefix for all custom action/filter hook names
Ensure PHP 7.4+ compatibility
Use type hints where appropriate (parameters, return types, properties)
Sanitize inputs, validate data, and escape outputs following WordPress security best practices; use nonces for forms/AJAX
Use the WordPress database API ($wpdb) for all database operations
Prefix functions and classes in the global namespace with edac_
Use WordPress transients for caching temporary data where appropriate
All user-facing text in PHP must be translatable using the accessibility-checker text domain
Use PHPDoc for all public classes, methods, and properties
Document all custom hooks (actions/filters) with docblocks including parameters and types
Files:
accessibility-checker.php
accessibility-checker.php
📄 CodeRabbit inference engine (.github/copilot-instructions.md)
Implement proper plugin activation and deactivation hooks
Files:
accessibility-checker.php
🧠 Learnings (4)
📚 Learning: 2025-08-26T11:25:48.236Z
Learnt from: pattonwebz
PR: equalizedigital/accessibility-checker#1208
File: includes/options-page.php:401-410
Timestamp: 2025-08-26T11:25:48.236Z
Learning: In the Accessibility Checker plugin, the edac_is_pro() function uses a robust detection pattern by checking both EDACP_VERSION (which comes from the pro plugin) and EDAC_KEY_VALID existence before looking at its value. This prevents PHP notices and ensures reliable pro feature detection.
Applied to files:
accessibility-checker.php
📚 Learning: 2025-08-29T11:15:35.151Z
Learnt from: CR
PR: equalizedigital/accessibility-checker#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-08-29T11:15:35.151Z
Learning: Applies to accessibility-checker.php : Implement proper plugin activation and deactivation hooks
Applied to files:
accessibility-checker.php
📚 Learning: 2025-07-18T01:29:35.548Z
Learnt from: SteveJonesDev
PR: equalizedigital/accessibility-checker#1088
File: includes/classes/Rules/Rule/EmptyParagraphTagRule.php:50-50
Timestamp: 2025-07-18T01:29:35.548Z
Learning: In the Accessibility Checker plugin, the 'wcag' field can use custom values like '0.1' to represent best practice rules and manual testing requirements that don't map directly to specific WCAG success criteria but are still important for accessibility compliance.
Applied to files:
accessibility-checker.php
📚 Learning: 2025-07-18T01:18:27.812Z
Learnt from: SteveJonesDev
PR: equalizedigital/accessibility-checker#1088
File: includes/classes/Rules/Rule/VideoPresentRule.php:41-42
Timestamp: 2025-07-18T01:18:27.812Z
Learning: In the Accessibility Checker plugin, the 'wcag' field can use custom values like '0.3' to represent best practice rules and manual testing requirements that don't map directly to specific WCAG success criteria but are still important for accessibility compliance.
Applied to files:
accessibility-checker.php
🪛 LanguageTool
readme.txt
[grammar] ~6-~6: There might be a mistake here.
Context: ...6.6 Tested up to: 6.8 Stable tag: 1.31.1 License: GPLv2 or later License URI: htt...
(QB_NEW_EN)
🔇 Additional comments (4)
readme.txt (2)
6-6: Stable tag bump synced. Clean work.Looks tight and matches the PHP header and package.json. I pity the bug that tries to slip in here.
6-6: Add a 1.31.1 changelog note.Bumping the stable tag without a corresponding “= 1.31.1 =” entry can confuse folks on wp.org. If this is a maintenance-only release, add a brief line like “Maintenance: version sync; no functional changes.”
package.json (1)
3-3: Version bump aligned across assets.package.json now matches readme.txt and the plugin header. Ship it.
accessibility-checker.php (1)
13-13: Header and EDAC_VERSION in lockstep.Version: 1.31.1 and define('EDAC_VERSION', '1.31.1') are consistent. No code-path changes introduced. All good, fool.
Also applies to: 39-39
William Patton (6):
Summary by CodeRabbit