Release v1.26.0 - #1031
Conversation
…pt-to-generate-filter-for-rules-to-make-testing-individual-rules-easier Add prompt to generate a WordPress filter for rule slugs
Backport: Release/1.25.0
…liam/pro-142-pro-add-action-or-build-script-to-auto-generate-new-pot2 Update translation files (POT/JSON)
…s when being output NOTE: that the pageScanner.bundle has no register or enqueue to handle it's translated strings (even though it has some) since it's injected by the checkPage script. This is an issue that I don't have a solution for yet. [PRO-142]
The pageScanner bundle and rules were not updated here, those need some additional handling that will be tackled in a later card [PRO-142]
…-action-or-build-script-to-auto-generate-new-pot2 Add a workflow that can make an updated pot file for the plugin
There was a problem hiding this comment.
Pull Request Overview
This PR bumps the release version to 1.26.0 and updates various components for the new release. Key changes include:
- Converting multiple imports of i18n functions from '@wordpress/i18n' to using the global "wp.i18n" object.
- Updating version numbers and stable tags in package.json and readme.txt.
- Adding a workflow for updating translation POT files and updating translation JSON files accordingly.
Reviewed Changes
Copilot reviewed 216 out of 216 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| src/frontendHighlighterApp/index.js | Changed i18n import to use global wp.i18n |
| src/frontendHighlighterApp/fixesModal.js | Changed i18n import to use global wp.i18n |
| src/frontendFixes/Fixes/skipLinkFix.js | Changed i18n import to use global wp.i18n |
| src/emailOptIn/index.js | Changed i18n import to use global wp.i18n |
| src/editorApp/index.js | Changed i18n import to use global wp.i18n |
| src/common/saveFixSettingsRest.js | Changed i18n import to use global wp.i18n |
| src/admin/summary/summary-tab-input-event-handlers.js | Changed i18n import to use global wp.i18n |
| src/admin/fixes-page/pro-callout.js | Changed i18n import to use global wp.i18n |
| readme.txt | Updated stable tag to 1.26.0 |
| package.json | Bumped version to 1.26.0 and added cypress dependency |
| languages/accessibility-checker.pot | Updated version details and POT creation date |
| Translation JSON files (all languages) | Updated translation revision dates and added php-format/js-format comments |
|
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 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![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 marks the v1.26.0 release of the Accessibility Checker plugin, focusing on enhancing its internationalization infrastructure and updating translation assets. It also introduces a new utility for developers and updates development tooling.
Highlights
- Internationalization Improvements: The plugin's JavaScript assets now explicitly register their translation files using
wp_set_script_translations. Additionally, the way i18n functions are imported in JavaScript files has been refactored to use thewp.i18nglobal, aligning with WordPress best practices. - Translation File Updates: Numerous JSON translation files have been added or updated, and the main Portable Object Template (POT) file has been refreshed to include new translatable strings and correct formatting flags.
- New Developer Utility: A new prompt file has been introduced, providing a template for generating WordPress filters to selectively register rules based on their slugs.
- Development Dependencies: Cypress has been added as a new development dependency, indicating potential enhancements to end-to-end testing.
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 is currently in preview and 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 to provide feedback.
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 updates the plugin to version 1.26.0, including updates to the plugin version, plugin version constant, translation files, and the addition of script translations for javascript files. It also includes minor code style changes for consistency.
…ckport-1.26.0 pre-backport 1.25.0 translation changes
…5 22:10:19909010 - Hebrew
…5 22:10:19909010 - Spanish (Spain)
…5 22:10:19909010 - Arabic
…5 22:10:19909010 - Romanian
…5 22:10:19909010 - German (Germany)
…5 22:10:19909010 - Chinese (Simplified)
…5 22:10:19909010 - Italian
…5 22:10:19909010 - French (France)
…5 22:10:19909010 - Polish
…5 22:10:19909010 - Portuguese (Portugal)
…5 22:10:19909010 - Thai
…5 22:10:19909010 - Dutch
…5 22:10:19909010 - Swedish
…5 22:10:19909010 - Greek
…5 22:10:19909010 - Japanese
…5 22:10:19909010 - Portuguese (Brazil)
…5 22:10:19909010 - Vietnamese
…5 22:10:19909010 - Korean
…5 22:10:19909010 - Danish
…5 22:10:19909010 - Norwegian (Bokmål)
…5 22:10:19909010 - Bulgarian
…5 22:10:19909010 - Czech
…5 22:10:19909010 - Estonian
…5 22:10:19909010 - Finnish
…5 22:10:19909010 - Hungarian
…5 22:10:19909010 - Indonesian
…5 22:10:19909010 - Lithuanian
…5 22:10:19909010 - Latvian
…5 22:10:19909010 - Slovak
…5 22:10:19909010 - Slovenian
…5 22:10:19909010 - Turkish
…5 22:10:19909010 - Ukrainian
…5 22:10:19909010 - Russian
…june-24-2025-22-10-19909010 PTC accessibility-checker (1985): Automatic Translations June 24, 2025 22:10:19909010
Changelog:
William Patton (4):