Update dependency cronstrue to ^3.3.0 (main)

[elastic-renovate-prod]

This PR contains the following updates:

Package	Type	Update	Change
cronstrue	dependencies	minor	^3.0.0 -> ^3.3.0

---

Release Notes

bradymholt/cronstrue (cronstrue)

v3.3.0

Compare Source

What's Changed

• Adding Serbian locale by @​MilosPaunovic in https://github.com/bradymholt/cRonstrue/pull/359

New Contributors

• @​MilosPaunovic made their first contribution in https://github.com/bradymholt/cRonstrue/pull/359

Full Changelog: bradymholt/cRonstrue@v3.2.0...v3.3.0

v3.2.0

Compare Source

What's Changed

• Fixed missing translation for Russian translation by @​dmitrymaslov13 in https://github.com/bradymholt/cRonstrue/pull/358

New Contributors

• @​dmitrymaslov13 made their first contribution in https://github.com/bradymholt/cRonstrue/pull/358

Full Changelog: bradymholt/cRonstrue@v3.1.0...v3.2.0

v3.1.0

Compare Source

What's Changed

• feat: Added Croatian Locale by @​Rookxc in https://github.com/bradymholt/cRonstrue/pull/357

New Contributors

• @​Rookxc made their first contribution in https://github.com/bradymholt/cRonstrue/pull/357

Full Changelog: bradymholt/cRonstrue@v3.0.0...v3.1.0

---

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 this update again.

---

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

---

This PR has been generated by Renovate Bot.

[elasticmachine]

Pinging @elastic/kibana-management (Team:Kibana Management)

[elastic-renovate-prod]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock

[07:32:31.834] INFO (222809): Installing tool [email protected]...
[07:32:32.834] WARN (222809): Npm error:
npm info it worked if it ends with ok
npm WARN npm npm does not support Node.js v22.17.1
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12.
npm WARN npm You can find the latest version at https://nodejs.org/
npm info using [email protected]
npm info using [email protected]
npm ERR! cb.apply is not a function
npm timing npm Completed in 768ms

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/containerbase-npm-l9y2qv/_logs/2025-09-24T07_32_32_799Z-debug.log
[07:32:32.860] ERROR (222809): npm install command failed
[07:32:32.861] FATAL (222809): Install tool yarn failed in 1s.

[elastic-renovate-prod]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 1cb8065

Failed CI Steps

• FTR Configs #2

Test Failures

• [job] [logs] FTR Configs #2 / Package policies Package Policy - upgrade when upgrading to a version with no breaking changes "after each" hook for "successfully upgrades package policy"

Metrics [docs]

✅ unchanged

History

• 💔 Build #351101 failed 3259637
• 💔 Build #347375 failed 94c8820
• 💛 Build #341005 was flaky d4cc363

[mattkime]

looks good and works well.

[kibanamachine]

Starting backport for target branches: 8.19, 9.1, 9.2

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

[kibanamachine]

💔 Some backports could not be created

Status	Branch	Result
❌	8.19	Backport failed because of merge conflicts
❌	9.1	Backport failed because of merge conflicts You might need to backport the following PRs to 9.1: - Expose isRetryableEsClientError (#228315) - [ResponseOps] Update nodemailer (#238816) - Update kibana-presentation misc canvas dependencies (main) (#235576) - Update dependency cssstyle to ^5.3.0 (main) (#236671) - [scout] extend playwright + no-floating-promises ESLint rules for tests in "packages" (#236302)
✅	9.2

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 235647

Questions ?

Please refer to the Backport tool documentation