chore(deps): update dependency io.karatelabs:karate-junit5 to v1.5.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
io.karatelabs:karate-junit5	1.5.0 → 1.5.2

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

karatelabs/karate (io.karatelabs:karate-junit5)

v1.5.2

Compare Source

No Breaking Changes

This release is mainly to

• ensure Karate works with the latest Java versions > 21
• update Gatling integration to avoid a warning in reports
• upgrade multiple library / dependencies because of CVEs or common conflicts.

Meet the Karate team in Paris on December 11, 2025 ! (Register here)

Fix List

Here is a complete list of all issues fixed in this release.

What's Changed

• #​2641 introduce @​fail tag to mark tests which are expected to fail by @​dve in #​2643
• Add an optional environment variable for docker images in order to easily and globally configure additional startup flags by @​abdallahghdiri in #​2649
• Support for Case-Sensitive HTTP Headers in Karate Mock Server by @​srmppn in #​2653
• [KeepOriginalHeaders] update document by @​srmppn in #​2656
• #​2660 fail annotation in xml report by @​dve in #​2661
• Upgrade json-smart from 2.5.1 to 2.5.2 fixing CVE-2024-57699 by @​julianladisch in #​2663
• #​2667 result count by @​dve in #​2668
• Dated version for Karate Gatling integration #​2677) Feature/gatling 3.11.5 by @​CPogX in #​2678
• fix #​2670 by @​ThierryLejeune in #​2674
• Issue 2482: accept empty cookies names by @​cranberrysoft in #​2676
• Karate UI - javascript error: Unexpected token #​2665 xpath parenthesis by @​CPogX in #​2675
• Add WebSocket frame aggregation support by @​jon-armen in #​2693
• clarify mvn quickstart command syntax for Windows PowerShell by @​markhughes321 in #​2695
• 2515 third revision logic in matchoperator by @​f-delahaye in #​2702
• 2707 by @​f-delahaye in #​2709
• Fix forward slashes being turned into escape by @​srmppn in #​2714

A Big Thank You

To all contributors, especially first-time contributors to Karate.

New Contributors

• @​dve made their first contribution in #​2643
• @​abdallahghdiri made their first contribution in #​2649
• @​srmppn made their first contribution in #​2653
• @​cranberrysoft made their first contribution in #​2676
• @​markhughes321 made their first contribution in #​2695

Full Changelog: karatelabs/karate@v1.5.1...v1.5.2

Artifacts Released

• Maven artifacts
• Standalone JAR (download below)
• Karate-Robot JAR (download below)
• Docker Image
• Repository SBOM report (download below)

v1.5.1

Compare Source

No Breaking Changes

This release is mainly to upgrade a couple of library / dependencies because of CVEs or common conflicts.

• Upgrade netty due to CVE-2024-47535
• Update classgraph to solve Quarkus related ExceptionInInitializerError

Fix List

Here is a complete list of all issues fixed in this release.

What's Changed

• Fixed readme for karate-gatling by @​debasisj in #​2608
• Bump commons-io:commons-io from 2.7 to 2.14.0 in /karate-demo by @​dependabot in #​2614
• Update Chrome DevTools Protocol by @​oxsoft in #​2590
• Update headless option by @​oxsoft in #​2592
• Upgrade JaCoCo to 0.8.12 by @​Godin in #​2635
• handle mp4 like any other media in Embed toMap() by @​CPogX in #​2638
• Add afterScenarioOutline & karate.scenarioOutline by @​OwenK2 in #​2636
• Improve readme by @​alaguna95 in #​2640

A Big Thank You

To all contributors, especially first-time contributors to Karate.

New Contributors

• @​debasisj made their first contribution in #​2608
• @​oxsoft made their first contribution in #​2590
• @​abdallah-rashwan made their first contribution in #​2628
• @​Godin made their first contribution in #​2635
• @​CPogX made their first contribution in #​2638
• @​OwenK2 made their first contribution in #​2636
• @​alaguna95 made their first contribution in #​2640

Full Changelog: karatelabs/karate@v1.5.0...v1.5.1

Artifacts Released

• Maven artifacts
• Standalone JAR (download below)
• Karate-Robot JAR (download below)
• Docker Image
• Repository SBOM report (download below)

---

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 was generated by Mend Renovate. View the repository job log.

[github-actions]

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Edit this PR description and add one of these lines:

• This PR fixes #123 or Fixes: #123

• This PR closes #123 or Closes: #123

• This PR resolves #123 or Resolves: #123

• Other supported keywords: fix, fixed, close, closed, resolve, resolved
  Option 2: Link via GitHub UI (Note: won't clear the failed check)

1. Go to the PR → Development section (right sidebar)

2. Click "Link issue" and select an existing issue

3. Push a new commit or re-run the workflow to clear the failed check
   Option 3: Use branch naming
   Create a new branch with one of these patterns:

• 123-feature-description (number at start)

• issue-123-feature-description (issue-number at start)

• feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.---

This comment was automatically generated by the issue linking workflow