RATATOSKRATATOSK
ログイン

Dapr

v1.18.5Orchestration & Management
2026年10月8日

OTHER 31

ワークフローの信頼性、スケジューラーの安定性、メッセージ配送の保証、可観測性、終了処理を対象とした修正リリースで、コンポーネント設定の追加も含まれます。オペレーターが対応すべき変更はありません。

その他の記録済み変更 31 件すべてfixes 20 · value changes 8 · additions 2 · constraints 1

fixes (20)

  • The activity actor now cuts the actor ID at the last two separators, which always delimit the numeric task ID and generation, so the full parent instance ID is recovered whatever characters it contains.
  • daprd now stops the meter it created for a runtime once that runtime has fully shut down, so the replacement runtime's meter is the only one exporting.
  • - With the default enableInOrderMessageDelivery: false, checkpointing happened fire-and-forget, independent of message delivery to the application.
  • - With enableInOrderMessageDelivery: true, the component waited for the handler to return before checkpointing, but checkpointed anyway when the handler responded RETRY.
  • - A handler failure is retried with the configured backoff until it succeeds or the subscription is cancelled, instead of being dropped and checkpointed anyway.
  • - Under concurrent handling, a partition's checkpoint advances only through the newest contiguous run of successful batches, and checkpoint writes for a partition are serialized so they can no longer race each other out of order.
  • - Checkpointing is skipped once the subscription is cancelled or partition ownership loss is observed, and a checkpoint-store failure now surfaces as an error instead of being silently swallowed.
  • When shutdown cancels the context, the component leaves the delivery unacknowledged so RabbitMQ can redeliver it after the connection closes.
  • A rebalance now stops the retries and the in-flight call to the application, the message is left unacknowledged, and the consumer that takes over the partition receives it again.
  • The Kafka component commits the offset when it sees that error and stops its own retry loop.
  • An activity result whose execution ID differs from the recorded scheduling of its task ID is acknowledged and dropped before it reaches the inbox, on every admission path.
  • A purge now invalidates the actor's cached state before it returns, unconditionally, whatever else in the purge failed.
  • Streaming calls that start once the gRPC API has begun shutting down are now rejected with Unavailable, instead of starting new goroutines.
  • Registering a callback stream now also returns once the stream manager has stopped, so the call ends as the sidecar shuts down.
  • The sidecar could stop processing actor placement updates after it tried to close its connection to the placement service.
  • This was introduced in 1.16.0.
  • Every start request carries an execution ID that is generated once and resent unchanged by each retry.
  • The loop now clears the flag while it still holds the queue lock, so a concurrent enqueue either lands before the empty check and is seen, or after the flag is cleared and starts a new loop.
  • The Anthropic component now translates toolChoice into the object Anthropic expects ([dapr/components-contrib#4542](https://github.com/dapr/components-contrib/pull/4542)):
  • advanced (checkpointed) their Event Hubs offsets without regard to whether the application actually handled the event successfully.

value changes (8)

  • The Secret is now mounted 0440.
  • The Scheduler now uses go-etcd-cron [v0.12.8](https://github.com/diagridio/go-etcd-cron/releases/tag/v0.12.8), which drops a trigger for a job that has already been deleted or overwritten and logs it, instead of stopping the engine.
  • Publishing now also stores the baggage in the CloudEvent, in a baggage field.
  • The Scheduler now uses go-etcd-cron with [pull request #136](https://github.com/diagridio/go-etcd-cron/pull/136), which retries the revoke with short attempts inside a 2 second budget.
  • - auto is omitted, since Anthropic already defaults to {"type":"auto"}.
  • - required and any become {"type":"any"}.
  • - none becomes {"type":"none"}.
  • - A tool name becomes {"type":"tool","name":"<tool name>"}.

additions (2)

  • - A new maxConcurrentHandlers option (default 100) bounds how many received-but-not-yet-checkpoint-eligible events can be in flight at once, pausing further receives once the bound is reached.
  • - A new subscription-level checkPointFrequencyPerPartition option controls how often the checkpoint is persisted for a partition (starting with the first batch, then every N contiguous successfully-processed batches, or never if set to 0); this only affects how far a restart may replay already-successful batches, not the correctness guarantee itself.

constraints (1)

  • - Both delivery modes now start from the earliest retained event when a consumer group has no stored checkpoint yet; an existing stored checkpoint always takes precedence.
Daprをスタックに追加

対応が必要なリリースが出たときに、週次メールでお知らせします。今回のように対応が不要な週は、メールを送りません。

スタックに追加 →
公式リリースノート ↗Daprのリリース一覧 →