← 전체 릴리스
Dapr 알림 받기
Daprv1.17.13
2026-08-14릴리스 노트 원문 ↗
확인할 변경이 있을 때만 주 1회, critical 보안 공지는 즉시 발송
중요 수정2
작업자 연결 해제 후 정지된 워크플로 복구 수정
영향 대상워크플로 버전 관리, 패치 적용 또는--max-body-size설정워크플로 버전을 사용할 수 없거나, 패치가 일치하지 않거나, 페이로드가 설정된 크기를 초과해 워크플로가 정지된 상태에서 모든 워크플로 작업자의 연결이 끊기면 비활성화가
actor is stalled오류로 실패할 수 있었습니다. 작업자가 다시 연결된 뒤에도 워크플로가STALLED상태로 남을 수 있어daprd를 재시작해야 했습니다. 작업자가 다시 연결되고 정지 조건이 충족되면 리마인더가 다시 전달되고, 타이밍에 좌우되거나daprd를 재시작하지 않아도 워크플로가 다시 실행됩니다.## Stalled workflows permanently stuck after the last workflow worker disconnects ### Problem A workflow that entered the `STALLED` state (version not available, patch mismatch, or payload size exceeded) could become permanently stuck if the last connected workflow worker disconnected while the workflow was stalled. Reconnecting workers, including workers registering the exact workflow version the stall was waiting for, did not resume it: status queries kept reporting `STALLED` and the only recovery was restarting daprd. When it occurred, the sidecar logged: ``` error while disconnecting work item stream: failed to deactivate workflow '<id>': actor is stalled ``` ### Impact Stalling exists precisely so that a workflow survives its workers going away and resumes once capable workers return, most commonly a rolling upgrade where the old application version disconnects and the new version reconnects. You were affected if you use workflow versioning, patching, or a configured `--max-body-size`, and all workflow workers of an application disconnected while a workflow was stalled; for example during application restarts, rolling upgrades, scale-to-zero, or behind a load balancer with `WorkflowsClusteredDeployment` enabled. ### Root Cause A stalled workflow actor parks its execution in-process, holding the execution reminder in flight until its context is cancelled, and marks its lock as stalled. When the last workflow worker disconnects, daprd unregisters the workflow actor types and deactivates all workflow actors, but deactivation begins by acquiring the actor's lock, and the lock rejects acquisition while the actor is stalled. Whether the workflow could later recover came down to a race: if the scheduler's reminder stream teardown cancelled the parked execution before deactivation reached the actor, deactivation succeeded and the unacknowledged reminder was redelivered when workers reconnected; if deactivation won the race, it failed with `actor is stalled`, leaving the actor activated and holding the reminder in flight, so reconnecting workers had nothing to redeliver and the workflow never re-executed. ### Solution Deactivating a stalled workflow actor now wakes the parked execution instead of failing: the held execution returns immediately, leaving the execution reminder unacknowledged, and deactivation completes. When workflow workers reconnect, the reminder is redelivered and the workflow re-executes, resuming and completing once the connected workers satisfy the stall condition (for example the required workflow version is registered, or daprd was restarted with a larger `--max-body-size`). Recovery from a stall no longer depends on timing, and a daprd restart is no longer required.
github.com/dapr/dapr/releases/tag/v1.17.13SPIFFE를 사용할 수 없을 때 Azure 자격 증명 체인의 폴백 수정
영향 대상클라이언트 시크릿이나 인증서 없이azureClientId와azureTenantId를 사용하는 Dapr 1.16.0 이상 Azure 컴포넌트 또는 다른 인증 방식보다spiffeworkloadidentity를 앞에 둔azureAuthMethods목록을 사용하는 Azure 컴포넌트이전에는 SPIFFE JWT SVID 소스를 사용할 수 없으면 자격 증명 체인이 SPIFFE 자격 증명에서 멈춰, 뒤에 동작하는 자격 증명이 있어도 시도하지 않고 인증에 실패했습니다. 이제 다음 자격 증명을 계속 시도합니다. SPIFFE 소스를 구성한 경우 동작은 바뀌지 않습니다.
## Azure component authentication halting at the SPIFFE credential instead of falling back ### Problem Azure (Microsoft Entra ID) components authenticate by trying a chain of credentials in order until one succeeds. When `azureClientId` and `azureTenantId` were set, the chain included the SPIFFE workload identity credential, and if no SPIFFE JWT SVID source was available the chain stopped at that step: ``` ChainedTokenCredential: failed to acquire a token. Attempted credentials: ClientAssertionCredential: failed to get JWT SVID source from context ``` Credentials later in the chain, such as managed identity or the Azure CLI, were never attempted, so the component failed to authenticate even though a working credential was available. ### Impact You were affected on Dapr 1.16.0 or later (where the SPIFFE credential joined the default chain) in either of these configurations: - An Azure component with `azureClientId` and `azureTenantId` set but no client secret or certificate, relying on a later credential in the default chain (for example managed identity or the Azure CLI). - An explicit `azureAuthMethods` list placing `spiffeworkloadidentity` before another method (for example `spiffeworkloadidentity,managedidentity`), expecting fallback when SPIFFE is not configured. ### Root Cause `ChainedTokenCredential` only continues past a credential that reports a `credentialUnavailableError`; any other error is treated as fatal and ends the chain. The SPIFFE credential returned a plain error when the context carried no JWT SVID source, so a missing prerequisite was treated as a fatal authentication failure rather than a signal to try the next credential. ### Solution The SPIFFE credential now reports itself as unavailable when no JWT SVID source is present, before any token request is made, which is exactly what `ChainedTokenCredential` requires to continue to the next credential in the chain. Both the default chain and explicitly ordered `azureAuthMethods` lists now fall through as expected, and behavior when a SPIFFE source is configured is unchanged.
github.com/dapr/dapr/releases/tag/v1.17.13
기능·개선1
컴포넌트 작업 호출 컨텍스트에 SPIFFE SVID 소스 추가
## SPIFFE SVID component operation propagation ### Problem The SPIFFE SVID source was not propagated to component operation calls. As a result, any component that wanted to use the SPIFFE ID for authentication had to capture the source in its `init` method and manage it explicitly. SDKs such as the Azure SDK, which can transparently use the SPIFFE SVID source when it is present on the context, were unable to do so. ### Impact Azure components could not leverage the SPIFFE ID for authentication without explicitly handling the source, and this also blocked future support for SPIFFE-based authentication in other components. ### Root Cause The SPIFFE SVID source was attached only to the component's `init` method context, not to the context passed into operation calls. ### Solution The SPIFFE SVID source is now attached to the context passed into operation calls, allowing components to use the SPIFFE ID for authentication on a per-operation basis.
github.com/dapr/dapr/releases/tag/v1.17.13
정리 내용은 AI가 작성하므로 틀릴 수 있으며, 보증 없이 제공합니다.