Bump com.github.tomakehurst:wiremock-jre8 from 2.32.0 to 3.0.1

[dependabot]

Bumps com.github.tomakehurst:wiremock-jre8 from 2.32.0 to 3.0.1.

Release notes

Sourced from com.github.tomakehurst:wiremock-jre8's releases.

3.0.1

🐛 Bug fixes

• Stop returning 500s for unmatched path patterns (#2339) @​Mahoney
• Ensure that the shadow JAR is always built last to ensure webhooks fat JAR wins (#2344) @​tomakehurst
• Added validation of UUIDs in path parameters in the admin API so that clearer errors are reported when non UUIDs are provided or item isn't found rather than throwing a 500 error (#2347) @​tomakehurst
• Respect StopAction in V1 Filter (#2335) @​Mahoney

Thanks to the regression reporters: @​defnngj , @​oleg-nenashev , @​Mahoney

WireMock 3.0.0

A new major release that introduces a lot of new features, enhancements and also some breaking changes. The key changes include support for Java 17, dropping Java 8 support, new matchers and dynamic response macros, new API endpoints, etc. We’ve made a small number of breaking changes to the Java API plus some behavioural changes, but the JSON (REST and file) API remains fully compatible with 2.x.

NOTE: A blog post with the user-friendly summary and migration guidelines is coming soon!

Thanks to all contributors! The changelog below represents key changes between 2.35.0 and 3.0.0. The full list of changes is available below in the collapsed section.

WARNING: There are known issues in the WireMock 3.0.0 release. Please be careful when updating, and see the Errata below

Upgrade guide

This guide assumes you would be upgrading from WireMock 2.35.0 to 3.1.0

1. If you aren’t using WireMock 2.35.0, upgrade to this version first
2. If you use WireMock Standalone, backup your configurations, logs and other information you might need in the future, just in case the - upgrade goes wrong
3. If you use the WireMock Webhooks Extension, delete the dependency on it and the downloads. Now the extension is a part of the WireMock core
4. If you use any WireMock extensions, private source or open source ones, ensure they are compatible with WireMock 3 by checking this GitHub Issue, documentation and the integration tests. If you discover any incompatible extension, please raise a bug in [wiremock/wiremock/issues (https://github.com/wiremock/wiremock/issues) or comment in [wiremock/wiremock #2323](wiremock/wiremock#2323), We will triage and route it accordingly
5. If you use Java 8 on the instance, update to Java 11 or Java 17
6. Update WireMock to the most recent release of WireMock 3

🚀 New features and improvements

• Matching and response templating:
• JSON matching via matchesJsonSchema() @​kapishmalik
• Form parameter matching support (#2157) @​kapishmalik
• not() matcher that inverts other matchers (#2006) @​SatyamAK
• Support for multi-stub mapping files to the remote loader function (#2198) @​DjerohN
• Support for Java time when serialising to/from JSON (#2130 ) @​mark-henry
• Support for matching multi-valued headers and query parameters with includes and hasExactly (#2110) @​kapishmalik
• Matching URLs by path template @​tomakehurst
• Matching path variables in the same manner as query, headers, etc. @​tomakehurst
• Support for addressing path variables by name in response templates @​tomakehurst

Proxy mode:

... (truncated)

Commits

• 34d4930 Bump patch version to 3.0.1
• ae6ed02 Stopped updating package-lock.json when bumping versions
• a302419 Fixed bump patch and minor versions logic
• ae525f9 Fixed get patch version function in build
• 0d4ccca Merge pull request #2347 from wiremock/better-stub-id-validation-in-admin-api
• c5e8230 Added validation of UUIDs in path parameters in the admin API so that clearer...
• 5273a43 Merge pull request #2339 from wiremock/fix-exception-in-diff
• ab05ee9 Ensured that the shadow JAR is always built last. Relocated dependencies in w...
• 9eaaa69 Merge pull request #2337 from wiremock/dependabot/gradle/com.diffplug.spotles...
• 36f04c7 Merge pull request #2343 from wiremock/semver-release-drafter
• Additional commits viewable in compare view

[matt-evervault]

Review: not safe to merge as-is

I checked usage of wiremock-jre8 across the codebase, read the WireMock 2.32.0 → 3.0.1 changelogs (2.33 – 2.35, 3.0.0, 3.0.1), and verified the build against the bumped version.

Usage: wiremock-jre8 is a testImplementation-only dependency, used in exactly two test files (WhenPerformingHttpRequestTests, WhenDealingWithHttpTimeoutsTests), via @WireMockTest / WireMockRuntimeInfo and the standard WireMock.* DSL (stubFor, get/post, urlEqualTo, aResponse, withHeader/withBody/withStatus/withFixedDelay, getRequestedFor/postRequestedFor, verify, RequestPatternBuilder). All of these are stable core APIs unaffected by the 3.x Java-API breaking changes (those are mostly around extensions/webhooks and standalone config) — no source changes would be needed on the Java-API side, and the com.github.tomakehurst.wiremock.* import paths are unchanged in 3.0.1 (the org.wiremock package/group rename happens in a later release, not here).

Build-breaking issue found: WireMock 3.0.0 dropped Java 8 support ("support for Java 17, dropping Java 8 support" — see the 3.0.0 release notes). Concretely, com.github.tomakehurst:wiremock-jre8:3.0.1 transitively pulls in org.wiremock:wiremock:3.0.1, which publishes Gradle module metadata declaring a minimum target JVM version of 11.

This repo intentionally supports Java 8:

• lib/build.gradle sets sourceCompatibility/targetCompatibility = JavaVersion.VERSION_1_8 for the whole module (main + test source sets).
• .github/workflows/sdk.yml runs the full test matrix against java-version: ['8', '11', '16', '17', '21'].

I bumped the version locally and ran gradle clean test. It fails immediately at dependency resolution (before any test even runs, and regardless of which JDK is used to run Gradle — this is a Gradle module-metadata compatibility check, not a runtime issue):

Could not resolve org.wiremock:wiremock:3.0.1.
  Required by:
      project :lib > com.github.tomakehurst:wiremock-jre8:3.0.1
  > Dependency resolution is looking for a library compatible with JVM runtime version 8,
    but 'org.wiremock:wiremock:3.0.1' is only compatible with JVM runtime version 11 or newer.

There's no minimal code fix for this: bytecode targeting 11 can't be produced by a Java 8 javac, so the java-version: 8 CI leg cannot compile the test sources at all once this bump lands, and current resolution already fails outright given the module's declared Java 8 target. Making it pass would require dropping Java 8 support from the SDK (removing it from the CI matrix and bumping sourceCompatibility), which is a deliberate compatibility/support decision for the maintainers, not something to fold into a dependency-bump PR.

(For context, the baseline build on master currently has 15 unrelated EndToEndTests failures in this sandbox due to missing live API credentials/network — the 25 + 6 WireMock-backed unit tests in the two files above pass cleanly on the current 2.32.0.)

Recommendation: hold this PR. Either:

1. ·@·d·ependabot i·gnore t·his major version to stop it being re-proposed until Java 8 support is intentionally dropped, or
2. If the team decides to drop Java 8 support, that should be a separate, deliberate PR (bump sourceCompatibility/targetCompatibility to 11, update the CI matrix) with this dependency bump layered on top.

No code changes pushed — the only way to make the build pass would be the Java 8 policy change above, which is outside the scope of this automated bump.

---

Generated by Claude Code