Update dependency org.http4k:http4k-format-moshi to v5 #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.40.1.0->5.13.4.0By merging this PR, the issue #2 will be automatically resolved and closed:
Release Notes
http4k/http4k (org.http4k:http4k-format-moshi)
v5.13.4.0Compare Source
v5.13.2.0Compare Source
v5.13.1.0Compare Source
v5.13.0.1Compare Source
different IDE settings
v5.13.0.0Compare Source
the imported module, and renaming your templates from .jade to .pug. Please see Pug4j docs for anything else.
v5.12.2.1Compare Source
VerifyWebhookSignaturefilter to ServerFilters as it's not for HTTP clients!v5.12.2.0Compare Source
if-none-match headerthe response lacks the etag header. H/T @efaselv5.12.1.0Compare Source
from HTTP message bodies (via
Body.json(::JsonNodeDataContainer)).toLens()v5.12.0.0Compare Source
using vanilla Jetty backend then this is a NoOp replacement, otherwise fallback to using the new
Jetty11module and then plan migration accordingly. MassiveH/T to H/T @FredNordin for the implementation upgrade.
Jetty11()instead ofJetty(), somigration should be very simple. Other renames as required (using
11) to avoid API clashes in the http4k codebase.AwsPreSignRequests. UseAwsRequestPreSignerinstead. H/T @oharaandrew314v5.11.1.0Compare Source
AwsPreSignRequestsclass. H/T @oharaandrew314http4k-serverless/lambda)
v5.11.0.0Compare Source
keys. The fix MAY break JSON serialisation (which actually is a bug as the expected behaviour is for the Enums to use
the predefined mapping).
v5.10.7.0Compare Source
v5.10.6.0Compare Source
v5.10.5.0Compare Source
v5.10.4.0Compare Source
v5.10.3.0Compare Source
v5.10.2.0Compare Source
v5.10.1.0Compare Source
constructing an OAuthProvider H/T @mbcltd
HttpMessages
v5.10.0.0Compare Source
v5.9.0.0Compare Source
v5.8.6.0Compare Source
v5.8.5.1Compare Source
v5.8.5.0Compare Source
Events.then()withEvents.and()for clarity.v5.8.4.0Compare Source
v5.8.3.0Compare Source
v5.8.2.0Compare Source
ExecutionService.withRequestTracing()to propagate Zipkin traces acrossthreads
v5.8.1.0Compare Source
v5.8.0.0Compare Source
v5.7.5.0Compare Source
v5.7.4.0Compare Source
extension! H/T @dmcg for the inspiration.
v5.7.3.0Compare Source
v5.7.2.0Compare Source
@mbcltd
v5.7.1.0Compare Source
investigation.
v5.6.5.0Compare Source
IntelliJ (as final line endings might be added automatically)
error
v5.6.4.0Compare Source
commons-codecversion. H/T @oharaandrew314v5.6.3.0Compare Source
v5.6.2.1Compare Source
v5.6.2.0Compare Source
v5.6.1.0Compare Source
Changelog:
v5.6.0.0Compare Source
nonBlank()to set of standard BiDiMappings. H/T @dmcgForm-fields are now filtered for values which are not blank. This means that you may need to change form lenses to be
optional and default to an empty string if they are missing.
v5.5.0.0Compare Source
break approval files for any tests.
v5.4.1.0Compare Source
@Serializable classes. H/T @krissrex
v5.4.0.0Compare Source
H/T @krissrex
v5.3.0.0Compare Source
templates. H/T @mikaelstaldal
v5.2.1.0Compare Source
v5.2.0.0Compare Source
explicitly used/extended the standard behaviour.
v5.1.2.1Compare Source
v5.1.2.0Compare Source
v5.1.1.1Compare Source
@oharaandrew314
v5.1.1.0Compare Source
v5.1.0.0Compare Source
WsResponseand
SseResponseobjects. This makes it easier to set response headers and control if a connection is made from theincoming request as it is no-longer hidden (it is exposed at the top level instead of being hidden in the SSE and
Websocket objects). It also means that the interfaces for the protocols follow the same pattern.
v5.0.0.0to
v4.48.0.0and then re-upgrade tov5.0.0.0. This will ensure that you only have to deal with Deprecationsbetween the major versions.
are on-pre Java 19 you can continue to use the old module version with no breaking changes.
versions will now be incoming with every major JDK release in order to track new and retired JVM features (6 month
cycle).
JettyLoom, based on Loom VirtualThreads. Requires Java 21 to use.Standard
Jettyremains usable with any Java version.SunHttpLoom, based on Loom VirtualThreads. Requires Java 21 to use.Standard
SunHttpremains usable with any Java version.use.
on TooTallNate/Java-Websocket. H/T @oharaandrew314
Requires Java >= 19 to use.
reflection-free JSON library.
Eventsimplementationto visually document your applications through testing. See example in reference guide.
v4.48.2.0the http4k Enterprise Edition subscription. Non-licensed parties should NOT use this version of http4k libraries. Either
downgrade to the Apache2 licensed v4.48.0.0, or contact us to arrange an http4k Enterprise Edition subscription.
v4.48.0.0Compare Source
v4.47.2.0Compare Source
v4.47.1.0Compare Source
v4.46.0.0Compare Source
Zipkin traces. Possible break
if you were relying on Zipkin state in a downstream handler. This change will allow better in-memory testing as traces
will be reported correctly inside the context of the filter.
take EventNode which is a tree node.
v4.45.0.0Compare Source
@mikaelstaldal
remove the
authorizationCodeparameter from your implementations and use the code from thetokenRequestv4.44.1.0Compare Source
v4.44.0.0Compare Source
fix, simply change from
GzipCompressionMode.Memory/StreamingtoGzipCompressionMode.Memory()/Streaming()v4.43.1.0Compare Source
v4.43.0.0Compare Source
AuthorizationCodeMissingerror.Fixes #895
v4.42.1.0Compare Source
v4.42.0.0Compare Source
in new dependency release might lead to some surprising changes in behaviour of matchers for comparing JSON nodes
v4.41.4.0Compare Source
redocUiWebjarfunction.redocUiLitefunction.swaggerUiWebjarnow works properly with a non-root path. Plusperformance improvements.
v4.41.3.0Compare Source
v4.41.2.0Compare Source
v4.41.1.1Compare Source
v4.41.1.0Compare Source
new
swaggerUiWebjarfunction. H/T @oharaandrew314swaggerUIin favor of newswaggerUiLitefunction, which uses a new config format.H/T @oharaandrew314
v4.41.0.0Compare Source
shouldn't cause any problems that we know about, but we are bumping the breaking version number just in case.
v4.40.2.0Compare Source