Bump @yoast/ai-frontend to 0.26.0 and drop the superseded AI suggestion styles

[JorPV]

Context

The bulk editor's AI suggestion field has been moved into @yoast/ai-frontend as a platform-agnostic SuggestionField component (Yoast/ai-frontend#164, Yoast/ai-frontend#165), so consumers other than WordPress — starting with wpseo-woocommerce for alt-text generation — can reuse it. That component shipped in @yoast/ai-frontend@0.26.0.

Free owns the build of the yoast-seo-ai-frontend-package asset, so SuggestionField only reaches window.yoast.aiFrontend once Free bumps the dependency. This PR does that bump, and drops the bulk editor CSS that the package now carries itself.

Related: Yoast/reserved-tasks#1427, Yoast/wordpress-seo-premium#5066.

Summary

This PR can be summarized in the following changelog entry:

• Non-user-facing: updates @yoast/ai-frontend to 0.26.0 and removes the bulk editor AI suggestion styles that now ship with the package.

Relevant technical choices:

• The dependency lives in packages/js/package.json, not the root manifest. @yoast/ai-frontend is on a 0.x version, where ^0.25.0 resolves to >=0.25.0 <0.26.0 — so the caret bump is required, not cosmetic, and yarn.lock travels in the same commit because CI installs with --frozen-lockfile.
• The two .yst-bulk-editor-ai-suggestion rules are removed rather than kept as a safety net. The gradient frame and the primary-50 textarea background are now part of the component itself (.frame and textarea.field in the package's styles.module.scss), so keeping them here would mean two sources of truth for the same look. After this PR, yst-bulk-editor-ai-suggestion appears nowhere in this repository.
• This PR is paired with Yoast/wordpress-seo-premium#5066 and the two should merge together. Premium trunk still applies yst-bulk-editor-ai-suggestion in generated-field-cell.js; 3.3.4 update not tagged #5066 is what replaces that markup with the package component. In the window between this PR merging and 3.3.4 update not tagged #5066 merging, anyone running Free trunk + Premium trunk sees the AI suggestion field without its gradient border. Nothing breaks — it is purely cosmetic, and only on trunk.

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

• Check out this branch and run yarn install, then grunt build:js and grunt build:css.
• Confirm the package resolved to 0.26.0: grep version node_modules/@yoast/ai-frontend/package.json.
• Activate Yoast SEO Premium on the branch of Yoast/wordpress-seo-premium#5066, so the bulk editor renders the package component.
• Go to Yoast SEO → Bulk editor and generate an AI suggestion for an SEO title or meta description.
• Confirm the Skeleton appears while the suggestion is being requested.
• Resize the screen while the skeleton is shown and confirm the second line is shorter for larger text areas.
• Confirm the suggestion appears in a field with the gradient border and a light purple background — the same look as before this change, now coming from the package instead of this stylesheet.
• Confirm Apply and Discard both still work.
• Confirm the browser console shows no errors, in particular no "Element type is invalid" from a missing export.
• Smoke test that the rest of the bulk-editor styles and the UsageCounter (sparks usage) in the AI generator or the AI content planner feature modal still look good/ aren't broken.

Relevant test scenarios

• Changes should be tested with the browser console open
• Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
• Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
• Changes should be tested on different browsers
• Changes should be tested on multisite

A missing or misnamed export from the bumped package surfaces as a console error rather than a visibly broken page, which is why the console should be open.

Test instructions for QA when the code is in the RC

• QA should use the same steps as above.

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

• The yoast-seo-ai-frontend-package script asset, which is built here and consumed by Premium. Other Free consumers of this package — UsageCounter in the AI generator (packages/js/src/ai-generator/components/app.js) and in the AI content planner feature modal (packages/js/src/ai-content-planner/components/feature-modal.js) — come along with the version bump and are worth a smoke test.
• The bulk editor page stylesheet (css/src/bulk-editor-page.css). Only the AI suggestion rules were touched; the surrounding error-alert and cell-value rules are unchanged.

Other environments

• This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.
• This PR also affects Yoast SEO for Google Docs. I have added a changelog entry starting with [yoast-doc-extension], added test instructions for Yoast SEO for Google Docs and attached the Google Docs Add-on label to this PR.

Documentation

• I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

• I have tested this code to the best of my abilities.
• During testing, I had activated all plugins that Yoast SEO provides integrations for.
• I have added unit tests to verify the code works as intended.
• If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
• I have written this PR in accordance with my team's definition of done.
• I have checked that the base branch is correctly set.
• I have run grunt build:images and committed the results, if my PR introduces or edits images or SVGs.

The component's own unit tests live in @yoast/ai-frontend; this PR carries no logic of its own.

Innovation

• No innovation project is applicable for this PR.
• This PR falls under an innovation project. I have attached the innovation label.
• I have added my hours to the WBSO document.

Fixes #1427

[coveralls-official]

Coverage Report for CI Build 0

Coverage remained the same at 59.538%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	30085
Covered Lines:	18391
Line Coverage:	61.13%
Relevant Branches:	19275
Covered Branches:	10997
Branch Coverage:	57.05%
Branches in Coverage %:	Yes
Coverage Strength:	100032.98 hits per line

---

💛 - Coveralls

[Copilot]

🟡 Changes recommended

The PR metadata (“Fixes #1427”) appears inconsistent with the actual changes (dependency bump + CSS removal), which risks auto-closing/associating the wrong issue.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates the Free plugin’s bundled yoast-seo-ai-frontend-package dependency so the new platform-agnostic SuggestionField (now shipped by @yoast/ai-frontend@0.26.0) is available on window.yoast.aiFrontend, and removes now-superseded bulk editor suggestion styling from this repo to avoid duplicate sources of truth.

Changes:

• Bump @yoast/ai-frontend from ^0.25.0 to ^0.26.0 in packages/js/package.json.
• Update yarn.lock to lock @yoast/ai-frontend to 0.26.0.
• Remove .yst-bulk-editor-ai-suggestion CSS overrides from css/src/bulk-editor-page.css (class no longer referenced in-repo).

File summaries

File	Description
packages/js/package.json	Bumps @yoast/ai-frontend to ^0.26.0 so the updated component export is available to consumers.
yarn.lock	Updates the lock entry to resolve @yoast/ai-frontend@0.26.0 under frozen installs.
css/src/bulk-editor-page.css	Removes bulk editor AI suggestion styles that are now shipped by the package itself.

Review details

• Files reviewed: 2/3 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.