fix(deps): update dependency org.http4k:http4k-bom to v6.56.0.0 - #79
Merged
Conversation
Contributor
Author
Branch automerge failureThis PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
|
renovate
Bot
force-pushed
the
renovate/http4k-monorepo
branch
2 times, most recently
from
July 28, 2026 08:14
ad1da80 to
0a48fed
Compare
renovate
Bot
force-pushed
the
renovate/http4k-monorepo
branch
from
July 28, 2026 14:57
0a48fed to
0352740
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
6.55.0.0→6.56.0.0Release Notes
http4k/http4k (org.http4k:http4k-bom)
v6.56.0.0Compare Source
data-on:click,data-bind:foo,data-computed:total) instead of the removed 0.x hyphen form.UpdateResult.ConditionFailedis now adata classcarrying the item to report back, rather than adata object.DeleteItemis now evaluated. TheConditionExpressionwas previously ignored outright, so a guarded delete always succeeded against the fake - including insidetransactWriteItems, where a failing condition now correctly cancels the transaction.PutItem,UpdateItemandDeleteItemgainReturnValuesOnConditionCheckFailure, so a failed conditional write can return the record which blocked it (DynamoDB reports it in the error body). The enum andTransactWriteItem's support for it already existed.Configuration
📅 Schedule: (in timezone Europe/Oslo)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.