Repository navigation
Maintenance: upgrade WireMock to 4.x #2663
Description
Activity
Warning
This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Summary
WireMock 3.13.2 resolves Jetty 11.0.26, Handlebars 4.3.1,
httpclient55.5.1, andhttpcore5/httpcore5-h25.3.6 in thepowertools-cloudformationandpowertools-lambda-metadatatests.Why is this needed?
These versions cause 18 open Dependabot alerts. Jetty 11 has no public patched release on Maven Central, and every WireMock release that fixes the alerts requires Java 17. #2597 raises the minimum to Java 17 and removes the blocker.
Which area does this relate to?
Tests
Solution
Upgrade WireMock to 4.0.0-beta.39 and add the
wiremock-junit5artifact, which WireMock 4 split out of the core library. WireMock 4 resolves Jetty 12.1.13, Handlebars 4.5.5,httpclient55.6.4, andhttpcore5/httpcore5-h25.4.3.Acknowledgment