[Deprecation Schedule] Remove deprecated palette functions

[weronikaolejniczak]

Summary

Removed euiPaletteForLightBackground and euiPaletteForDarkBackground. Updated docs to use euiTheme.colors.vis.euiColorVisTextX.

Why are we making this change?

Related to #1469

Removal of the deprecated functions was planned for December 2025.

Screenshots #

Impact to users

🔴 This is a breaking change. It removes deprecated palette functions.

Kibana (0 usages):

• euiPaletteForLightBackground
• euiPaletteForDarkBackground

Cloud UI (0 usages):

• euiPaletteForLightBackground
• euiPaletteForDarkBackground

It can still affect other consumers.

QA

Specific checklist

• Verify there is no regression on the Data viz > Sizing page (staging, prod)

General checklist

• Browser QA
  • Checked in both light and dark modes
  • Checked in both MacOS and Windows high contrast modes
    • (emulate forced colors if you do not have access to a Windows machine.)
  • Checked in mobile
  • Checked in Chrome, Safari, Edge, and Firefox
  • Checked for accessibility including keyboard-only and screenreader modes
• Docs site QA
  • Added documentation
  • Props have proper autodocs (using @default if default values are missing) and playground toggles
  • Checked Code Sandbox works for any docs examples
• Code quality checklist
  • Added or updated jest and cypress tests
  • Updated visual regression tests
• Release checklist
  • A changelog entry exists and is marked appropriately
  • If applicable, added the breaking change issue label (and filled out the breaking change checklist)
  • If the changes unblock an issue in a different repo, smoke tested carefully (see Testing EUI features in Kibana ahead of time)
• Designer checklist
  • If applicable, file an issue to update EUI's Figma library with any corresponding UI changes. (This is an internal repo, if you are external to Elastic, ask a maintainer to submit this request)

[github-actions]

This PR contains breaking changes. The opener of this pull request is asked to perform the following due diligence steps below, to assist EUI in our next Kibana upgrade:

• If this PR contains prop/API changes:
  • Search through Kibana for <EuiComponent usages (example search)
  • In the PR description or in a PR comment, include a count or list with the number of component usages in Kibana that will need to be updated (if that amount is "none", include that information as well)
• If this PR contains CSS changes:
  • Search through Kibana for the changed EUI selectors, e.g. .euiComponent (example search)
  • In the PR description or in a PR comment, include a count or list with the number of custom CSS overrides in Kibana that will need to be updated (if that amount is "none", include that information as well)
• 🔍 Tip: When searching through Kibana, consider excluding **/target, **/*.snap, **/*.storyshot files to reduce noise and only look at source code usages
• ⚠️ For extremely risky changes, the EUI team should potentially consider the following precautions:
  • Using a pre-release release candidate to test Kibana CI ahead of time
  • Using kibana-a-la-carte for manual QA, and to give other Kibana teams a staging server to quickly test against

Log | Bot Usage

[mgadewoll]

🟢 Change LGTM, and the updated docs don't have any regression. Thanks for the cleanup!

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 93cd3ae
• Documentation website
• Storybook

History

• 💚 Build #2336 succeeded 4cf1430

cc @weronikaolejniczak

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 93cd3ae

History

• 💚 Build #5526 succeeded 4cf1430

cc @weronikaolejniczak