Update dependency @redocly/cli to ^1.32.2 (main)

[elastic-renovate-prod]

This PR contains the following updates:

Package	Type	Update	Change	Pending
@redocly/cli	devDependencies	patch	^1.32.0 -> ^1.32.2	1.33.1 (+1)
@redocly/cli	dependencies	patch	^1.32.0 -> ^1.32.2	1.33.1 (+1)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[afharo]

/ci

[afharo]

/ci

[kibanamachine]

Starting backport for target branches: 9.0

https://github.com/elastic/kibana/actions/runs/13798951662

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 627617c

Failed CI Steps

• Jest Tests #9

Test Failures

• [job] [logs] Jest Tests #9 / notesSlice notesReducer fetchNotesByDocumentIds should replace notes when success on fetch notes by document ids on a non-empty state
• [job] [logs] Jest Tests #9 / notesSlice notesReducer fetchNotesBySavedObjectIds should replace notes when success on fetch notes by saved object id ids on a non-empty state

Metrics [docs]

✅ unchanged

History

• 💚 Build #282785 succeeded b752cf206f25cad943014e80c24eed8e13aea3d7

cc @afharo

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	9.0	Backport failed because of merge conflicts You might need to backport the following PRs to 9.0: - Update dependency @openfeature/core to ^1.7.2 (main) (#212462) - Update dependency deepmerge to ^4.3.1 (main) (#206165) - Update dependency @redocly/cli to ^1.32.0 (main) (#212624) - [Streams] Replay loghub data with synthtrace (#212120)

Manual backport

To create the backport manually run:

node scripts/backport --pr 213914

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213914 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213914 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213914 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213914 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213914 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213914 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213914 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213914 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213914 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 213914 locally

[afharo]

I (think that I) finally managed to fix CI in the backport PR: #213913

Once merged, I'll retry this backport

[kibanamachine]

Starting backport for target branches: 9.0

https://github.com/elastic/kibana/actions/runs/14071933286

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	9.0	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 213914

Questions ?

Please refer to the Backport tool documentation

[afharo]

Skipping this backport because we're about to merge #215038.
We'll make sure to backport that one instead.