fix(deps): update non-major dependency updates that can be auto-merged - #186
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/minor-patch-group
branch
3 times, most recently
from
August 16, 2026 15:29
f5b8348 to
11311b9
Compare
renovate
Bot
force-pushed
the
renovate/minor-patch-group
branch
from
August 16, 2026 23:27
11311b9 to
ad895c7
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.1.2→6.1.36.1.2→6.1.36.2.3→6.2.41.64.0→1.65.01.6.1→1.6.22.51.2→2.53.013.2.0→13.3.013.2.0→13.3.06.57.1.0→6.57.2.03.20260801.105040→3.20260811.0514233.20260805.065922→3.20260807.1025276.20260724.114851→6.20260813.115012Release Notes
kotest/kotest (io.kotest:kotest-assertions-core-jvm)
v6.2.4Compare Source
What's Changed
copiesin shouldContainExactCopies must be 1 or higher by @alfonsoristorato in #6207New Contributors
Full Changelog: kotest/kotest@6.2.3...v6.2.4
open-telemetry/opentelemetry-java (io.opentelemetry:opentelemetry-bom)
v1.65.0Compare Source
NOTE: The
opentelemetry-exporter-zipkinartifact has stopped being published. It wasdeprecated in a prior release. Users should migrate to OTLP or use a Zipkin-compatible collector
exporter.
API
ImmutableBaggage.put(#8658)
NumberFormatExceptionin baggage decoder(#8593)
TraceStateBuilder.removecorrupting the builder when the same key is removed twice(#8613)
Incubating
BoundLongCounter,BoundDoubleCounter,BoundLongHistogram,BoundDoubleHistogram,BoundLongUpDownCounter,BoundDoubleUpDownCounter,BoundLongGauge,BoundDoubleGauge) to the incubator metrics API(#8527)
Extensions
JaegerPropagatorbaggage header key case sensitivity(#8496)
JaegerPropagator(#8632)
OtTracePropagatorextract(#8631)
jaeger-baggageheader after 64 tokens, including malformedtokens (#8702)
SDK
AttributesMap) to enforce last-value-win semantics basedon string value of
AttributeKey.getKey()(#8548)
Traces
Samplershutdown lifecycle:Samplernow extendsCloseableand exposes a defaultshutdown()invoked when theSdkTracerProvideris shut down;JaegerRemoteSamplerimplementsit to stop its polling executor
(#8574)
Metrics
PeriodicMetricReaderself-observability metrics by internal telemetry version(#8597)
error.typeon failed collections inPeriodicMetricReader(#8650)
LongExemplarAssert.hasFilteredAttributesSatisfyingExactlyto enforce exactattribute matching
(#8518)
Logs
ReadWriteLogRecorddefaultgetObservedTimestampEpochNanosreturning the record timestamp(#8504)
Profiles
(#8514)
Exporters
opentelemetry-exporter-zipkin; the artifact is no longer published(#8677)
HttpExporterwarning logs(#8428)
OkHttpHttpSendermTLS when using the platform default trust store(#8565)
LogRecordflags in the low-allocation log marshaler(#8493)
OkHttpHttpSender,JdkHttpSender, andUpstreamGrpcSendershutdown toawait executor/channel termination
(#8495,
#8627,
#8624)
(#8626)
(#8637)
(#8364)
PrometheusHttpServer.toBuilder()dropping the configured default handler(#8619)
SystemOutLogRecordExporter(#8609)
LoggingMetricExportertoString(#8623)
Extensions
(#8669)
(#8668)
getStringListresolver inDeclarativeConfigPropertyUtil(#8572)
jsonschema2pojowith a hand-rolled POJO generator(#8600)
(#8450)
Shims
(#8674)
(#8511)
(#8635)
nullfromTracerShimextract when the carrier has no span context(#8505)
SpanContextwhen it is sampled but invalid(#8634)
Project tooling
version.gradle.kts(#8591)
(#8655)
http4k/http4k (org.http4k:http4k-bom)
v6.57.2.0Compare Source
CreateJob,DescribeJob,DescribeJobExecution,ListJobExecutionsForThing,CancelJob,DeleteJob), the stream operations devices pull files over MQTT from (CreateStream,DescribeStream,ListStreams,UpdateStream,DeleteStream) andDescribeEndpoint.Storage<StoredJob>and aStorage<StoredStream>.GetPendingJobExecutions,DescribeJobExecution(including$next),StartNextPendingJobExecutionandUpdateJobExecution. It signs asiot-jobs-dataagainst the account'sdata.jobs.iot.<region>.amazonaws.comendpoint.Storage<StoredJob>asFakeIot, so one store passed to both gives the control plane and the device API a single jobs state.ConditionalCheckFailed.Messageis now read from themessagefield DynamoDB actually sends (lower-cased, as on its other error bodies), so deserialising a real conditional-write failure no longer throws instead of returning theItemthe caller asked for. DynamoDB Local spells itMessage, so both are accepted. The property keeps its name, so existing callers compile; the fake now emits the same spelling as AWS.SQSMessagegainssystemAttributes(theAttributesmap SQS reports on a received message);SentMessageandSendMessageBatchResultEntrygain the previously-droppedMD5OfMessageSystemAttributes;ReceiveMessagegainsMessageSystemAttributeNames, the selector which supersedes the deprecatedAttributeNames. The attribute names SQS uses are available asMessageSystemAttributeName, andMessageFieldsDto.toSqs()is now public so the checksums can be computed outside the module. All new fields are defaulted, and each type keeps its previous primary constructor as a secondary, so existing bytecode still links (only the syntheticcopyof adata classunavoidably changes shape).MessageGroupId,MessageDeduplicationIdandMessageSystemAttributesare recorded alongside theSenderId,SentTimestampand (on a.fifoqueue)SequenceNumberSQS itself populates, andReceiveMessagereports them inAttributes, honouring the request's selection. A.fifoqueue now deduplicates as SQS does: repeating aMessageDeduplicationIdwithin 5 minutes of the accepted send succeeds and reports the originalMessageId/SequenceNumberwithout enqueueing again - but with the checksums of the request just received, since SQS digests what it was sent even when it deduplicates it away.FakeSQSgains defaulteddeduplication,queueConfigandclockconstructor parameters.attribute_type(#a, :t)- the only form real DynamoDB accepts, with the type passed as an expression attribute value - now parses, resolved through the request'sExpressionAttributeValues. It previously failed to parse (escaping as a 500 onUpdateItem), so conditions written for the real service could not run against the fake. The bare-name form (attribute_type(a, S)), which the fake has always accepted and real DynamoDB rejects, still parses.#nameor:value(or a malformedattribute_typeoperand) is now reported as the 400ValidationExceptionthe real service answers with, instead of escaping as a 500 - by the conditional writes (PutItem/UpdateItem/DeleteItem/TransactWriteItems) as well asScan/Query. As at DynamoDB it is a request error, checked before the expression is evaluated, soAND/ORshort-circuiting cannot hide it - and it stays distinct from theConditionalCheckFailedExceptiona condition which resolved and came out false still produces.PutItem,UpdateItem,DeleteItemandBatchWriteItemnow serialise their read-modify-write on the table storage - the monitorTransactWriteItemsalready synchronises on - so two concurrent writes to the same table can no longer both read the pre-write table and have the loser overwrite the winner.AdminSetUserMFAPreferenceandSetUserMFAPreferenceactions (withSMSMfaSettingsType/SoftwareTokenMfaSettingsType/EmailMfaSettingsType/WebAuthnMfaSettingsTypemodels), so a user's MFA factors can be enabled and a preferred factor chosen. The fake supports both.capralifecycle/liflig-logging (no.liflig:liflig-logging)
v3.20260811.051423Compare Source
capralifecycle/liflig-document-store (no.liflig:liflig-document-store)
v3.20260807.102527Compare Source
capralifecycle/liflig-http4k-setup (no.liflig:liflig-http4k-setup)
v6.20260813.115012Compare Source
Configuration
📅 Schedule: (in timezone Europe/Oslo)
* * * * 0,6)* 6-14 * * 1)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.