RATATOSK
← リリース一覧

Daprv1.19.2

セキュリティ 2破壊的変更 14重大な修正 11機能・改善 1依存関係の更新 1その他の変更 13

Daprの通知を受け取る

週次メールは確認すべき変更がある週だけ、深刻度がcriticalのセキュリティアドバイザリは即時に届きます。

アップグレード前の確認事項

既知の問題2
Redis Cluster のトランザクションがハッシュスロット間で部分的に適用される可能性

すべてのキーが同じハッシュタグを共有する場合に限り、トランザクションはアトミックに実行されます。それ以外の場合、スクリプトはハッシュスロットごとに実行されるため、あるスロットでETagが一致しないと、他のスロットへの書き込みが適用されたままになることがあります。最初のトランザクションでは警告がログに記録されます。

On Redis Cluster, a transaction is atomic only when all of its keys share a hash tag, such as `{order1}a` and `{order1}b`.
Otherwise the component runs one script for each hash slot, and an ETag mismatch in one slot can leave the writes of other slots applied. The component logs a warning about this on the first transaction.
github.com/dapr/dapr/releases/tag/v1.19.2
ストアごとのキー未存在時の ETag 動作

ETag を設定すると、Azure Cosmos DB、MongoDB、Redis ではキーが作成されます。RavenDB では first-write を使用している場合にキーが作成されます。ETag を指定して存在しない Azure Cosmos DB アイテムを削除しても、削除は成功します。

A set with an ETag on a key that does not exist behaves as in earlier releases.
On Azure Cosmos DB, MongoDB and Redis it creates the key, and on RavenDB it creates the key when the set also uses `first-write`.
On Azure Cosmos DB, a delete with an ETag on a missing item still succeeds.
github.com/dapr/dapr/releases/tag/v1.19.2

セキュリティ2

go-jose のサービス拒否脆弱性の修正

影響対象運用者が指定した RSA 署名鍵を使った Sentry の JWT 発行

このような鍵の法(modulus)が 4096 ビットを超える場合、daprd とコントロールプレーンのサービスはトラストバンドルを読み込めず、failed to parse JWT bundle で停止します。Sentry が生成する RSA-2048 鍵には影響しません。

原文を表示
- [Security: Fixes go-jose denial of service - CVE-2026-116587, CVE-2026-116586](#security-go-jose-denial-of-service)
github.com/dapr/dapr/releases/tag/v1.19.2

go-jose の解析脆弱性の修正

影響対象Dapr のトラストバンドルと Sentry の JWT 解析

従来の go-jose バージョンには、これらの解析経路でサービス拒否や JSON 解析時のクラッシュを引き起こす脆弱性がありました。このアップグレードで修正されます。Sentry での JWT 発行に、オペレーターが指定した 4096 ビットを超える RSA 署名鍵を使用すると、daprd とコントロールプレーンのサービスは failed to parse JWT bundle というエラーで停止します。Sentry が生成する RSA-2048 鍵には影響しません。

原文を表示
## Security: go-jose denial of service
### Problem
An upstream dependency of Dapr, `github.com/go-jose/go-jose/v4`, had three vulnerabilities in v4.1.4:
- [CVE-2026-116587](https://github.com/go-jose/go-jose/security/advisories/GHSA-mgcc-cww5-fp2q) (high): denial of service when go-jose parses a JWK that contains an RSA key.
- [CVE-2026-116586](https://github.com/go-jose/go-jose/security/advisories/GHSA-vvm8-gf78-28g4) (medium): a crash during JSON parsing.
- [CVE-2026-116585](https://github.com/go-jose/go-jose/security/advisories/GHSA-4w3g-jfj2-cw2q) (medium): a panic during CBC-HMAC processing.
### Impact
Dapr calls go-jose only through `go-spiffe`. It parses the JWKS in the trust bundle when the trust anchors load, and it parses the JWT that Sentry issues to the sidecar. These inputs come from the Dapr control plane, not from application requests.
CVE-2026-116587 and CVE-2026-116586 are on these paths in daprd and in each control plane service. Both are denial of service. CVE-2026-116585 is in JWE decryption, which Dapr does not use.
### Root Cause
Dapr pinned go-jose at v4.1.4. go-jose v4.1.5 fixes CVE-2026-116586 and CVE-2026-116585, and v4.1.6 fixes CVE-2026-116587.
### Solution
This release upgrades `github.com/go-jose/go-jose/v4` from v4.1.4 to v4.1.6.
go-jose v4.1.6 rejects an RSA key with a modulus larger than 4096 bits in a JWK. This affects you only if both of these conditions are true:
- JWT issuing is on in Sentry.
- You supply your own RSA JWT signing key that is larger than 4096 bits.
In that case, daprd and the control plane services cannot load the trust bundle, and they stop with the error `failed to parse JWT bundle`. Before you upgrade, replace the key with an RSA key of 4096 bits or fewer, or with an EC key. The JWT signing key that Sentry generates is RSA-2048, and it is not affected.
github.com/dapr/dapr/releases/tag/v1.19.2

破壊的変更14

ステートストアのETagとfirst-writeチェックの一貫性向上

影響対象ETag または first-write による同時実行制御を利用し、AWS DynamoDB、Azure Cosmos DB、CockroachDB、etcd、インメモリ、MongoDB、MySQL、Oracle Database、PostgreSQL(v1 および v2)、RavenDB、Redis、SQLite、または SQL Server(v1 および v2)を使用する構成

以前は、期限切れのキーがETagに一致する場合があり、チェックに失敗しても書き込みや部分的なトランザクションが実行されたり、同時実行されたetcdの書き込みがスキップされても成功と報告されたり、CockroachDBのETagが古いままになったりすることがありました。現在は、期限切れのキーはETagに一致しません。first-write はキーが存在しない場合、または期限切れの場合に成功し、それ以外の場合は失敗します。チェックに失敗すると、ETag不一致が返されます(HTTPでは409、gRPCではAborted)。

原文を表示
## State stores did not enforce ETags and first-write consistently
### Problem
Several state store components accepted a write or a delete that its ETag or its `first-write` concurrency option should have rejected, or rejected one that should have succeeded.
The behavior differed from one component to the next:
- **Expired keys.** A key whose TTL had passed, but that the store had not removed yet, still matched an ETag. A set or a delete with that ETag succeeded on a key that a read no longer returned. On some stores a `first-write` set on such a key was rejected as if the key still existed.
- **Transactions.** On Redis, a transaction with a failed ETag check still applied its other operations. On AWS DynamoDB and RavenDB, a delete inside a transaction ignored its ETag. On MongoDB, a transaction that failed to commit reported success.
- **Concurrent writes.** etcd read the key to check the ETag or `first-write` and then wrote in a separate request. When another write landed in between, a set, a delete or one operation of a transaction was skipped and the request still reported success.
- **Stale ETags.** On CockroachDB, every set without an ETag on an existing key left the ETag at the same value, so an ETag read before the write still matched after it.
- **Error type.** On SQL Server, a rejected `first-write` set returned a generic error. On Azure Cosmos DB and AWS DynamoDB, an ETag mismatch inside a transaction returned a generic error.
### Impact
You were affected if you use ETags or `first-write` concurrency with one of these state stores: AWS DynamoDB, Azure Cosmos DB, CockroachDB, etcd, in-memory, MongoDB, MySQL, Oracle Database, PostgreSQL (v1 and v2), RavenDB, Redis, SQLite or SQL Server (v1 and v2).
Depending on the store, a concurrent update could be lost without an error, a transaction could be applied in part, or a caller could not tell an ETag mismatch from another failure.
After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.
Requests that do not set an ETag and do not use `first-write` behave as before.
### Root Cause
The components checked the ETag against the stored row without checking whether the row had expired.
Some components checked the ETag in one request and wrote in another, or sent each operation of a transaction with its own condition, so a failed condition did not stop the other operations.
### Solution
Dapr now uses components-contrib v1.19.2, in which an ETag does not match a key that has expired, a `first-write` set succeeds on a key that is missing or expired and fails otherwise, and a failed check returns an ETag mismatch.
- [State stores did not enforce ETags and first-write consistently](#state-stores-did-not-enforce-etags-and-first-write-consistently)
github.com/dapr/dapr/releases/tag/v1.19.2

AWS DynamoDB ステートストアで期限切れアイテムの ETag が一致しなくなる変更

影響対象AWS DynamoDB ステートストアの set および delete 操作

以前は、期限切れのアイテムでも ETag が一致する場合があり、読み取りではアイテムが返されないにもかかわらず、set または delete が成功することがありました。現在は、このようなリクエストは ETag 不一致として失敗し、HTTP ステータス 409 または gRPC コード Aborted が返されます。

根拠“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
原文を表示
| AWS DynamoDB | A set or a delete with an ETag no longer matches an expired item. A `first-write` set succeeds on an expired item. A delete in a transaction checks its ETag. A failed condition in a transaction returns an ETag mismatch. |
github.com/dapr/dapr/releases/tag/v1.19.2

AWS DynamoDBのトランザクション内削除におけるETagチェックの修正

影響対象AWS DynamoDBで削除またはETag条件を含むトランザクション

トランザクション内の削除処理では、これまでETagが無視され、ETag条件の不一致が一般的なエラーとして報告されることがありました。現在は削除処理でETagが確認され、条件が不一致の場合はETag不一致(HTTPステータス 409 またはgRPCコード Aborted)が返されます。

根拠“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
原文を表示
| AWS DynamoDB | A set or a delete with an ETag no longer matches an expired item. A `first-write` set succeeds on an expired item. A delete in a transaction checks its ETag. A failed condition in a transaction returns an ETag mismatch. |
github.com/dapr/dapr/releases/tag/v1.19.2

ETag を指定しない set での CockroachDB 保存済み ETag のインクリメント

影響対象CockroachDB のステートストア

ETag を指定しない set が既存のキーを対象とした場合、保存済みの ETag は変更されず、書き込み前に読み取った ETag が書き込み後も一致していました。この set の後、保存済みの ETag がインクリメントされるようになりました。

原文を表示
| CockroachDB | A set without an ETag increments the ETag of the stored row. A delete with an ETag no longer matches an expired row. |
github.com/dapr/dapr/releases/tag/v1.19.2

CockroachDB で TTL 切れの行に対する ETag 削除の不一致

影響対象TTL を有効にした行があり、ETag に基づく削除を行う CockroachDB ステートストア

行の TTL が過ぎていてもストアによって削除されていない場合、読み取りではキーが返されないにもかかわらず、その行の ETag を使った削除が成功することがありました。アップグレード後は ETag の不一致により削除が失敗します(HTTP ステータス 409 または gRPC コード Aborted)。

根拠“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
原文を表示
| CockroachDB | A set without an ETag increments the ETag of the stored row. A delete with an ETag no longer matches an expired row. |
github.com/dapr/dapr/releases/tag/v1.19.2

etcd の ETag と first-write のチェックを書き込みと原子的に実行

影響対象etcd で ETag または first-write を使用する set、delete、トランザクション操作

チェックと書き込みを別々に行う間に別の書き込みが発生すると、set、delete、トランザクション操作が実行されないまま、リクエストが成功として報告されることがありました。現在は、このようなリクエストは ETag 不一致として失敗し、HTTP ステータス 409 または gRPC コード Aborted が返されます。

原文を表示
| etcd | Set, delete and transactions check ETags and `first-write` in the same etcd transaction as the write. A failed check applies nothing and returns an ETag mismatch. An ETag that is not a number returns an invalid ETag error. |
github.com/dapr/dapr/releases/tag/v1.19.2

インメモリ状態ストアの期限切れキー判定の修正

影響対象インメモリ状態ストアのETag操作および first-write セット

キーのTTLが切れていてもストアから削除されていない場合、読み取りではキーが返されなくなっているにもかかわらず、ETag付きの書き込みや削除が成功することがありました。また、一部のストアでは first-write によるセットが、キーがまだ存在するかのように拒否されていました。現在は、そのようなキーに対するETagリクエストはETag不一致となり、HTTPステータス 409 またはgRPCコード Aborted で失敗します。一方、first-write によるセットは成功します。

根拠“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
原文を表示
| In-memory | An ETag no longer matches an expired key, and a `first-write` set succeeds on one. Operations in a transaction are checked in order, so each one sees the earlier ones. |
github.com/dapr/dapr/releases/tag/v1.19.2

MongoDB で期限切れドキュメントの ETag による削除が一致しなくなる

影響対象削除に ETag を使用する MongoDB ステートストア

ドキュメントの TTL が過ぎてもストアによって削除されていない場合、読み取りではキーが返されなくなっているにもかかわらず、ETag を指定した削除が成功することがありました。アップグレード後は、ETag の不一致により削除が失敗します(HTTP では 409、gRPC では Aborted)。

根拠“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
原文を表示
| MongoDB | A delete with an ETag no longer matches an expired document. A set with an ETag treats an expired document as missing. A transaction returns the error of a failed commit. |
github.com/dapr/dapr/releases/tag/v1.19.2

MongoDB の ETag 付き set で期限切れドキュメントを未存在として扱う

影響対象ETag を使用する MongoDB の set 操作

ドキュメントの TTL が切れていてもストアによって削除されていない場合、読み取りでキーが返されなくなった後も、ETag を指定した set が成功することがありました。現在は、そのようなリクエストは ETag の不一致として失敗します(HTTP ステータス 409 または gRPC コード Aborted)。

根拠“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
原文を表示
| MongoDB | A delete with an ETag no longer matches an expired document. A set with an ETag treats an expired document as missing. A transaction returns the error of a failed commit. |
github.com/dapr/dapr/releases/tag/v1.19.2

ステートストアで期限切れ行の ETag 削除が不一致に

影響対象MySQL、Oracle Database、PostgreSQL、または SQLite のステートストア

TTL の期限が過ぎてもストアから削除されていない行は、読み取りでキーが返されなくなった後も、ETag を指定して削除できる場合がありました。今後はこのような削除は ETag の不一致として失敗し、HTTP ステータス 409 または gRPC コード Aborted が返されます。

根拠“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
原文を表示
| MySQL, Oracle Database, PostgreSQL, SQLite | A delete with an ETag no longer matches an expired row. |
github.com/dapr/dapr/releases/tag/v1.19.2

RavenDBトランザクション内の削除時のETag検証

影響対象ETagを伴う削除を含むRavenDBトランザクション

以前は、トランザクション内の削除でETagが無視されていました。アップグレード後は、ETagが一致しない場合、HTTPステータス 409 またはgRPCコード Aborted が返されます。

原文を表示
| RavenDB | A `first-write` set without an ETag fails when the document exists and has not expired. A delete in a transaction checks its ETag. |
github.com/dapr/dapr/releases/tag/v1.19.2

Redis トランザクションの書き込みをすべて成功または失敗に統一

影響対象ETag または first-write を使用する Redis トランザクション

以前は、ETag チェックに失敗しても、トランザクション内のほかの操作が実行されることがありました。現在は書き込み前にすべての ETag と first-write オプションを確認するため、チェックに失敗すると、そのトランザクションの書き込みはすべて行われません。

根拠“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
原文を表示
| Redis | A transaction runs as one script that checks every ETag and `first-write` option before it writes, so it applies all of its operations or none. A set applies its value and its TTL in the same script. A delete with an ETag that is not a number returns an invalid ETag error. |
github.com/dapr/dapr/releases/tag/v1.19.2

SQL Serverの期限切れ行に対するETagチェックの修正

影響対象ETagを使用するSQL Serverステートストア操作

行のTTLが期限切れになっていても、まだ削除されていない場合、読み取りではキーが返されなくなった後も、一致するETagを指定した書き込みや削除が成功することがありました。このようなリクエストは、ETag不一致として失敗するようになりました。HTTPでは 409、gRPCでは Aborted が返されます。

根拠“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
原文を表示
| SQL Server | A set or a delete with an ETag no longer matches an expired row. A `first-write` set succeeds on an expired row, and returns an ETag mismatch when the key exists. |
github.com/dapr/dapr/releases/tag/v1.19.2

Azure Cosmos DBトランザクションでのETag不一致に対する個別エラー

影響対象Azure Cosmos DB トランザクション

以前は、トランザクション内でETagが一致しない場合に汎用エラーが返され、ほかの失敗と区別できませんでした。現在はHTTP 409またはgRPC Abortedが返されます。

根拠“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
原文を表示
| Azure Cosmos DB | An ETag mismatch in a transaction returns an ETag mismatch error. A transaction that deletes a missing item no longer fails. |
github.com/dapr/dapr/releases/tag/v1.19.2

重大な修正11表面化しなかった不具合1

  • 生ペイロード publish のトレース修正
    影響対象rawPayload が true に設定され、gRPC の BulkPublishEvent、または HTTP の /v1.0-alpha1/publish/bulk と /v1.0/publish を使用し、パブリッシャーとサブスクライバー間でトレースを行う生ペイロードの publish

    以前は、gRPC または HTTP 経由の一括 publish、および HTTP 経由の単一 publish で、パブリッシャーのトレースを引き継がずに別個のサブスクライバートレースが開始されることがありました。また、pub/sub コンポーネントが一括 publish をネイティブに実装していない場合、HTTP の一括 publish では baggage が失われることもありました。現在は、影響を受ける各メッセージのメタデータに publish のトレースコンテキストと baggage が含まれ、一括 publish ではエントリーごとにプロデューサースパンが開始されます。

    ## Raw payload publishes over HTTP and raw bulk publishes did not carry trace context
    ### Problem
    When an app published with `rawPayload` set to `true`, the sidecar did not add the trace context of the publish to the message for these calls:
    - Bulk publish over gRPC (`BulkPublishEvent`) and HTTP (`/v1.0-alpha1/publish/bulk`).
    - Single publish over HTTP (`/v1.0/publish`).
    The subscriber's sidecar started a new trace for each message instead of continuing the publisher's trace.
    Over HTTP bulk publish, baggage was also lost unless the pub/sub component implements bulk publish natively.
    ### Impact
    You were affected if you publish raw payloads with one of these calls and trace across the publisher and the subscriber.
    Each delivery appeared as a separate trace, not linked to the publish.
    Single raw publishes over gRPC and publishes with a cloud event envelope were not affected.
    ### Root Cause
    With a cloud event envelope, the sidecar writes the trace context into the envelope.
    A raw payload has no envelope, so the trace context has to go into the message metadata, where the subscriber's sidecar reads it.
    Only single publish over gRPC did that. The other calls added only the baggage.
    HTTP bulk publish added the baggage to the request metadata, and the sidecar's built-in bulk publisher does not pass request metadata on to each message.
    
    
    For raw payload publishes over gRPC and HTTP, single and bulk, the sidecar now adds the trace context and the baggage to the metadata of each message.
    Bulk publishes start one producer span per entry, as bulk publishes with a cloud event envelope already do.
    - [Raw payload publishes over HTTP and raw bulk publishes did not carry trace context](#raw-payload-publishes-over-http-and-raw-bulk-publishes-did-not-carry-trace-context)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • HTTP および gRPC の一括パブリッシュにおけるメタデータ伝播の修正表面化しなかった不具合
    影響対象リクエストレベルのメタデータを指定した HTTP または gRPC 経由の一括パブリッシュ

    以前は、独自のメタデータマップを持たないエントリーには、ttlInSeconds や partitionKey などのリクエストレベルのキーが適用されませんでした。そのため、Redis などのコンポーネントでは、リクエストレベルの ttlInSeconds だけを指定したメッセージが期限切れになりませんでした。現在は、リクエストレベルのメタデータがすべてのエントリーに適用され、エントリーレベルのキーが優先されます。リクエストレベルの rawPayload には影響しません。

    ## Bulk publish ignored request-level metadata for entries without their own metadata
    ### Problem
    When publishing events in bulk, metadata set on the request, such as `ttlInSeconds` or `partitionKey`, was only applied to entries that also carried metadata of their own.
    Entries with no metadata were published without the request-level metadata.
    For example, publishing two entries with `ttlInSeconds=300` on the request, where only the first entry set its own `partitionKey`, produced a cloud event with an `expiration` field on the first entry and none on the second.
    ### Impact
    You were affected on Dapr 1.19.0 and 1.19.1, and on earlier releases, if you used the bulk publish API over HTTP or gRPC with request-level metadata.
    Most SDK bulk publish calls, such as `PublishEvents` in the Go SDK and `publish_events` in the Python SDK, build entries with no per-entry metadata, so for those callers request-level metadata had no effect at all.
    On components whose message TTL is handled by Dapr rather than natively, such as Redis, messages published with only a request-level `ttlInSeconds` never expired.
    Other request-level keys that a component reads per message, such as a partition key, were not applied either.
    The only workaround was to repeat the metadata on every entry.
    ### Root Cause
    The HTTP and gRPC bulk publish handlers merged request-level metadata into an entry only when the entry already had a metadata map.
    An entry with no metadata had none, so the merge was skipped and no request-level key reached it.
    The merge itself already handled an entry without metadata correctly; only the guard around it skipped the call.
    ### Solution
    Both handlers now merge request-level metadata into every entry.
    Entry-level keys keep precedence over request-level keys, matching the documented behavior of bulk publish and of the single publish API.
    `rawPayload` is still read from request-level metadata before the entries are processed and is unaffected.
    - [Bulk publish ignored request-level metadata for entries without their own metadata](#bulk-publish-ignored-request-level-metadata-for-entries-without-their-own-metadata)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • MongoDB のコミット失敗時のエラー報告を修正
    影響対象MongoDB トランザクション

    MongoDB のトランザクションでコミットに失敗した際、成功として報告されていましたが、コミットエラーを返すようになりました。

    | MongoDB | A delete with an ETag no longer matches an expired document. A set with an ETag treats an expired document as missing. A transaction returns the error of a failed commit. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • サイドカー接続プールのアプリ・名前空間単位の接続管理
    影響対象mTLSを有効にしたアプリのうち、リモートアプリのアクターまたはワークフローを呼び出すもの

    アプリがリモートアプリのアクターまたはワークフローを呼び出す際、ポッドで別のアプリのIPアドレスが再利用されると、以前のアプリの接続が使われ、Unavailable またはハンドシェイク時の unexpected SPIFFE ID エラーで呼び出しに失敗することがありました。現在は、そのアドレスにある別のアプリへの呼び出しでは、そのアプリの認証情報が使われます。新しい接続が確立されると、そのアドレスにある他のアプリ向けのアイドル接続は閉じられ、使用中の接続は処理を完了します。

    - [Actor and workflow calls kept failing after a pod IP was reused by a different app](#actor-and-workflow-calls-kept-failing-after-a-pod-ip-was-reused-by-a-different-app)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • actorStateStore が false のステートストアのホットリロード時の読み込み修正
    影響対象アクターが有効で、actorStateStore が false に設定されたステートストアを使うホットリロード

    以前は、サイドカーの実行中にこのようなストアを追加または変更すると、アクターのステートストアがすでに読み込まれている場合にスキップされ、再起動するまで呼び出しに失敗していました。false が環境変数やシークレットから設定された場合も同様でした。ステートプロセッサーがそのストアをアクターのステートストアとして指定しない場合、ストアが読み込まれ、ステート API から利用できるようになりました。

    - [A state store with actorStateStore set to false was not hot reloaded](#a-state-store-with-actorstatestore-set-to-false-was-not-hot-reloaded)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • サイドカーの接続プールでアプリを区別
    影響対象リモートアプリ上のアクターまたはワークフローへの mTLS 有効な呼び出し

    Kubernetes が停止した Pod の IP アドレスを別のアプリに再利用した際、サイドカーが以前のアプリへの接続を使い続け、unexpected SPIFFE ID のハンドシェイクや、アクターまたはワークフローの呼び出しで Unavailable が発生していました。現在は新しいアプリの認証情報を使って接続し、そのアドレスにある別のアプリ向けのアイドル接続を閉じます。使用中の接続は処理が終わるまで維持されます。

    ## Actor and workflow calls kept failing after a pod IP was reused by a different app
    ### Problem
    The sidecar keeps one gRPC connection per remote address for calls to other sidecars, such as actor invocation and workflow calls between apps.
    The mTLS credentials of a connection pin the namespace and app ID of the peer it was created for, and gRPC reuses them every time the connection reconnects.
    The connection pool was keyed by address only.
    When Kubernetes gave the IP of a stopped pod to a pod of a different app, the sidecar kept using the connection created for the previous app.
    Every handshake failed with `unexpected SPIFFE ID`, and every actor or workflow call to the new app on that address failed with `Unavailable`.
    ### Impact
    You were affected if mTLS is enabled, your apps call actors or workflows on a remote app, and the IP of a pod was reused by a pod of a different app.
    Calls from a sidecar to that address kept failing until the sidecar stopped calling it for 3 minutes (`DAPR_GRPC_MAX_CONN_IDLE`) or the target pod got a new IP.
    With steady traffic, that did not happen. Calls to other pods of the same app were not affected.
    Deleting the pod that received the reused IP recovered it.
    ### Root Cause
    The pool looked up an existing connection by address, and the identity the connection expects was not part of the lookup.
    Before Dapr 1.15 the actor call path closed the connection when a call failed with `Unavailable`, which hid the problem.
    Since 1.15 it does not, and nothing else closes a connection that is in use.
    Service invocation and the gRPC proxy still close the connection on `Unavailable`, so they recovered.
    ### Solution
    The connection pool is now keyed by address, namespace and app ID.
    A sidecar that finds a different app at an address it has used before dials a new connection with the credentials for that app.
    Connections to the same address, namespace and app ID are still shared.
    When a sidecar dials a new connection to an address, it also closes the idle connections it holds there for other apps, which can no longer succeed. Connections that are in use are left to finish.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • Placementの順序外確認応答によるハングの修正
    影響対象アクター状態ストアを指定せずにアクター型を宣言しているアプリ

    このようなアプリのサイドカーがPlacementに接続した際、同じ名前空間で他に接続しているアクターサイドカーが1つだけの場合、Placementが順序外のロック解除応答を待ち続けることがありました。その結果、新しいサイドカーが準備完了にならず、アクターの配置も変わらなくなっていました。Placementは、サイドカーのみのテーブルコピーに対する確認応答を、現在の更新ステップに一致する場合にのみカウントするようになりました。

    ## Actor sidecars stopped becoming ready after a sidecar without an actor state store joined
    ### Problem
    The Placement service could stop sending placement tables in a namespace.
    After that, every new sidecar in the namespace waited for its table and never became ready, and actor placement in the namespace stopped changing.
    The Placement service did not recover on its own.
    ### Impact
    You were affected if an app declares actor types but has no actor state store, and its sidecar connects to Placement when only one other sidecar with actors is connected in the namespace.
    New sidecars in that namespace did not become ready until the Placement leader restarted.
    ### Root Cause
    A sidecar that declares actor types but has no actor state store reports its host to Placement twice when it connects.
    Placement answers each report with a copy of the placement table sent to that sidecar only, and ignores the sidecar's acknowledgements of that copy.
    After the second copy, Placement counted the sidecar's acknowledgements as part of a namespace-wide update that was not running.
    With two sidecars in the namespace, that was enough to finish the phantom update, and Placement asked the other sidecar to unlock with no timeout set.
    The other sidecar ignored that request because it was out of sequence, and Placement waited for its answer indefinitely.
    ### Solution
    Placement now counts an acknowledgement only when it is for the current step of the update.
    - [Actor sidecars stopped becoming ready after a sidecar without an actor state store joined](#actor-sidecars-stopped-becoming-ready-after-a-sidecar-without-an-actor-state-store-joined)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • キュー内の処理を再試行する前にスケジューラーが並行実行制御を解放
    影響対象workflowConcurrencyLimits と globalMaxConcurrentWorkflowInvocations、または activityConcurrencyLimits と globalMaxConcurrentActivityInvocations を設定した Dapr 1.19.0 または 1.19.1 の環境

    名前ごとの上限とグローバル上限の両方を設定している場合、スロット待ちの処理は、インスタンスの完了後もキューに残り、同じ種類の無関係なワークフローまたはアクティビティが完了するまで再試行されないことがありました。その結果、処理数が設定した上限を大きく下回る状態になっていました。

    ## Workflows and activities with per-name concurrency limits stalled in the Scheduler
    ### Problem
    When a workflow or activity name had a per-name concurrency limit and the matching global limit was also set, work waiting for a free slot was not started when a running instance completed.
    It stayed queued until some unrelated workflow or activity of the same type completed.
    ### Impact
    You were affected on Dapr 1.19.0 and 1.19.1 if, in the `workflow` section of the Dapr Configuration, you set a per-name limit together with the global limit of the same kind:
    `workflowConcurrencyLimits` with `globalMaxConcurrentWorkflowInvocations`, or `activityConcurrencyLimits` with `globalMaxConcurrentActivityInvocations`.
    Per-name limits set without the matching global limit were not affected.
    Workflows and activities with those names ran far below their configured limit. With a per-name limit of 1, only 1 of 10 queued activities ran in about 45 seconds.
    ### Root Cause
    With both limits set, a workflow or activity holds two concurrency gates in the Scheduler: one for its type (the global limit) and one for its name (the per-name limit). Waiting work queues on the type gate.
    When an instance completed, the Scheduler released the type gate and tried to start waiting work before it released the name gate. That attempt failed because the name gate was still held, and the work was queued again.
    Releasing the name gate a moment later did not retry it, so the work waited for the next unrelated release.
    ### Solution
    The Scheduler releases all the gates held by a completed workflow or activity before it tries to start waiting work.
    - [Workflows and activities with per-name concurrency limits stalled in the Scheduler](#workflows-and-activities-with-per-name-concurrency-limits-stalled-in-the-scheduler)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 親サイドカーによるディスパッチ済みアプリ間ワークフロー/アクティビティ結果の受け入れ
    影響対象WorkflowAccessPolicyを使用し、アプリ間の子ワークフローまたはアクティビティ結果を扱うアプリ

    以前は、親サイドカーが子ワークフローの完了結果とアプリ間アクティビティの結果を不正な形式として扱っていたため、子が再試行を続ける間、子ワークフローは RUNNING のまま無期限にとどまっていました。親サイドカーをアップグレードすると、子の次回の再試行で結果が届けられます。結果を受け入れるのは、タスクのディスパッチ先アプリからのものに限られ、ワークフロー履歴の署名が有効な場合はアテステーションの検証も引き続き行われます。

    ## Cross-app child workflows never completed when the parent app had a workflow access policy
    ### Problem
    When a workflow called a child workflow on another app, and a `WorkflowAccessPolicy` applied to the parent workflow's app, the parent never received the child's result.
    The child completed, but the parent stayed `RUNNING` indefinitely, and the child kept re-sending its result on a reminder.
    The parent's sidecar rejected every delivery with `access denied by workflow access policy: malformed request for method 'AddWorkflowEvent'`.
    ### Impact
    You were affected on Dapr 1.19.0 and 1.19.1 if a `WorkflowAccessPolicy` applied to an app and a workflow of that app called a child workflow on another app.
    Every such parent workflow waited for its child indefinitely.
    No rule in the policy could let the result through, so removing the policy from the parent app was the only workaround.
    Workflows that called activities on another app were not blocked. The activity result was rejected in the same way, but then reached the parent through the activity result reminder. Each rejection still logged a warning and incremented `dapr_runtime_workflow_acl_action_denied_total`.
    ### Root Cause
    The parent's sidecar checks every call from another app against its workflow access policy.
    It works out the operation from the type of history event the call carries, and it only recognised terminate, raise event, pause and resume.
    A child workflow's completion or an activity's result is none of these, so the check treated the call as malformed and denied it before evaluating any rule.
    ### Solution
    The parent's sidecar no longer evaluates a child workflow's completion or an activity's result against the policy rules.
    These are replies to tasks the parent workflow dispatched, not operations another app performs on it.
    Instead, the parent accepts a result from another app only when the task was dispatched to that app, and denies it from any other app.
    The parent still verifies the result's attestation when workflow history signing is on.
    Only the sidecar of the parent's app needs the upgrade. After it, the child's next retry delivers the result and stuck parent workflows continue on their own.
    - [Cross-app child workflows never completed when the parent app had a workflow access policy](#cross-app-child-workflows-never-completed-when-the-parent-app-had-a-workflow-access-policy)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • actorStateStore: false のホットリロード処理を修正
    影響対象actorStateStore が false に設定されたステートストア

    以前は、別のアクターステートストアが読み込まれている状態で対象のストアを追加または変更すると、ホットリロードでそのストアがスキップされ、State API から利用できず、daprd を再起動するまで呼び出しが失敗していました。ホットリロードでは、重複エントリーの優先順位や {appID} の展開を含め、ステートプロセッサーによる評価を使うようになりました。環境変数とシークレットの値はコピー上で解決されます。不明な値がある場合もストアには引き続きマークが付けられ、アプリにスコープされていないコンポーネントは解決されません。

    A state store component with the `actorStateStore` metadata set to `"false"` was never loaded when it was added or updated through hot reload while an actor state store was already loaded.
    Daprd logged `Skipping hot reload of <store>: <actor store> is already the actor state store, only one actor state store is allowed`, and the store stayed unavailable to the state API.
    The same happened when the value came from an environment variable or a secret that resolves to `"false"`.
    You were affected if hot reload is enabled, actors are enabled, and you added or changed a state store component that sets `actorStateStore` to false while the sidecar was running.
    Calls to that state store failed until daprd was restarted.
    Stores that omit the `actorStateStore` metadata were not affected.
    To keep a second actor state store from being loaded, the hot reload reconciler skips a state store that is marked as the actor state store.
    It decided that from the presence of the `actorStateStore` metadata alone, while the state processor makes a store the actor state store only when the value is true.
    The reconciler now builds the metadata of the component as the state processor does, and applies the state processor's own check to it, including which of duplicate entries wins and how placeholders such as `{appID}` expand.
    When the `actorStateStore` value comes from an environment variable or a secret, the reconciler resolves it on a copy of the component first.
    A store is skipped only when the state processor would make it the actor state store.
    A value that cannot be known, because its secret store is not loaded, its secret read fails or its metadata cannot be built, still marks the store, as before.
    Components that are not scoped to the app are not resolved.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • インメモリ状態ストアのトランザクション操作の順次評価
    影響対象複数の操作を含むインメモリ状態ストアのトランザクション

    同じトランザクション内では、各操作に先行する操作の影響が反映されます。

    | In-memory | An ETag no longer matches an expired key, and a `first-write` set succeeds on one. Operations in a transaction are checked in order, so each one sees the earlier ones. |
    github.com/dapr/dapr/releases/tag/v1.19.2

機能・改善1

  • 不整合なワークフローインスタンスの強制パージ

    利用条件 --force フラグ

    Force purging a workflow instance failed when the instance metadata declared more inbox or history entries than exist in the state store.
    The request returned an error such as `inbox key 'inbox-000000' declared in metadata (inboxLength=2) but missing from state store`, and all of the instance's state and reminders were left in place.
    You were affected if you have workflow instances that were saved with an inbox count larger than the number of stored inbox entries.
    An inbox accounting bug in earlier releases, fixed by [#10155](https://github.com/dapr/dapr/pull/10155), could save an instance in this state, including instances created on Dapr 1.17.
    Since Dapr 1.18.0 these instances cannot be loaded, so get, terminate, purge and force purge all failed with the same error, and the instance's reminders kept retrying.
    The only way to remove such an instance was to delete its keys from the state store by hand.
    Force purge loaded the instance with the same strict check as every other workflow operation, which rejects state whose metadata declares an entry that is missing.
    It also built its list of keys to delete from the entries it had loaded, not from the counts declared in the metadata.
    Force purge now loads the entries that exist and skips the ones that are confirmed missing.
    It deletes every key the metadata declares, along with the instance's reminders.
    All other workflow operations keep the strict check and still fail for these instances.
    To remove an affected instance, run `dapr workflow purge <instance-id> --force`.
    - [Workflow force purge failed on instances with missing inbox or history entries](#workflow-force-purge-failed-on-instances-with-missing-inbox-or-history-entries)
    github.com/dapr/dapr/releases/tag/v1.19.2

依存関係の更新1

  • github.com/andybalholm/brotli の v1.2.7 への更新

    以前のデコンプレッサーは、各メタブロックに割り当てるメモリ量を制限していませんでした。v1.2.7でこの問題が修正されています。

    CVE-2026-111497GHSA-c9gr-gmg4-2vqvGO-2026-6888
    ## Security: brotli denial of service
    ### Problem
    An indirect dependency of Dapr, `github.com/andybalholm/brotli`, had a vulnerability in v1.2.1:
    - [CVE-2026-111497](https://github.com/andybalholm/brotli/security/advisories/GHSA-c9gr-gmg4-2vqv) ([GO-2026-6888](https://pkg.go.dev/vuln/GO-2026-6888)): the brotli decompressor did not limit the memory that it allocates for each meta-block. A small crafted brotli stream can make it allocate hundreds of megabytes for each kilobyte of input. This causes a denial of service.
    ### Impact
    Dapr uses brotli only through the Meilisearch search component (`search.meilisearch`) and its `meilisearch-go` client.
    That client decompresses brotli data only when the code that creates the client sets a content encoding.
    The Dapr Meilisearch component does not set a content encoding, so Dapr does not decompress brotli data.
    Vulnerability scanners and `govulncheck` report this vulnerability for Dapr 1.19.0 and 1.19.1, because both releases include brotli v1.2.1.
    ### Root Cause
    Dapr pinned brotli at v1.2.1. brotli v1.2.7 fixes CVE-2026-111497.
    ### Solution
    This release upgrades `github.com/andybalholm/brotli` from v1.2.1 to v1.2.7.
    - [Security: Fixes brotli denial of service - CVE-2026-111497](#security-brotli-denial-of-service)
    github.com/dapr/dapr/releases/tag/v1.19.2
その他の変更13
  • AWS DynamoDB の期限切れアイテムへの first-write セットが成功
    | AWS DynamoDB | A set or a delete with an ETag no longer matches an expired item. A `first-write` set succeeds on an expired item. A delete in a transaction checks its ETag. A failed condition in a transaction returns an ETag mismatch. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • Azure Cosmos DBで項目が存在しない場合の削除失敗の修正
    | Azure Cosmos DB | An ETag mismatch in a transaction returns an ETag mismatch error. A transaction that deletes a missing item no longer fails. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 数値以外の etcd ETag に対する無効な ETag エラーの返却
    | etcd | Set, delete and transactions check ETags and `first-write` in the same etcd transaction as the write. A failed check applies nothing and returns an ETag mismatch. An ETag that is not a number returns an invalid ETag error. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • RavenDB first-write set の失敗
    | RavenDB | A `first-write` set without an ETag fails when the document exists and has not expired. A delete in a transaction checks its ETag. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • Redis ステートストアの set 操作で値と TTL を単一スクリプトで設定
    | Redis | A transaction runs as one script that checks every ETag and `first-write` option before it writes, so it applies all of its operations or none. A set applies its value and its TTL in the same script. A delete with an ETag that is not a number returns an invalid ETag error. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 数値以外のETagを指定したRedis削除時の無効なETagエラー返却
    | Redis | A transaction runs as one script that checks every ETag and `first-write` option before it writes, so it applies all of its operations or none. A set applies its value and its TTL in the same script. A delete with an ETag that is not a number returns an invalid ETag error. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • SQL Server の first-write セットで期限切れキーと既存キーを区別
    | SQL Server | A set or a delete with an ETag no longer matches an expired row. A `first-write` set succeeds on an expired row, and returns an ETag mismatch when the key exists. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • Redis Cluster以外のRedisデプロイメントに対する本番利用警告の削除
    For other Redis deployments, the component no longer logs that Redis should not be used as an actor state store in production.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • AWS DynamoDB、etcd、RavenDBのトランザクションにおけるキー単位のETag処理
    AWS DynamoDB, etcd and RavenDB accept one operation for each key in a transaction.
    For several operations on one key, these components send the last operation with the ETag or `first-write` option of the first one.
    A later operation on that key that carries an ETag, or a `first-write` set after a set, fails with an ETag mismatch.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 削除後に同じキーを設定するトランザクションでのETag不一致
    The exception is a transaction that deletes a key and then sets the same key with an ETag: on Azure Cosmos DB, MongoDB and Redis that set fails with an ETag mismatch, because the version the ETag refers to is gone.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • ETag 操作のないトランザクションでのインメモリステートストアの ETag パス省略
    The in-memory store skips the ETag pass for a transaction in which no operation has an ETag or `first-write`.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • MongoDBでのETag削除を単一コマンド化
    On MongoDB 4.4 and later, a delete with an ETag is a single delete command.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • Redis ステートストアの EVALSHA によるスクリプト送信
    The Redis component sends its script by hash (`EVALSHA`), and sends the script body only when the server has not cached it.
    github.com/dapr/dapr/releases/tag/v1.19.2

整理した内容は AI が作成するため誤っている可能性があり、無保証で提供されます。