# Dapr v1.17.11

2026-07-17 · [元のリリースノート](https://github.com/dapr/dapr/releases/tag/v1.17.11) · [全体のまとめ](https://ratatosk.io/ja/releases/dapr/v1.17.11)

重大な修正 2 · その他の変更 2

## 重大な修正 (2)

### アクターのリマインダー一覧におけるメタデータの修正

- 影響対象: ID に `||` を含むアクター

> Listing reminders for actors whose IDs contain `||` now also reports the correct actor metadata.

### SchedulerにおけるDapr準拠のリマインダー名、ジョブ名、アクター IDの受け入れ

- 影響対象: Schedulerをバックエンドとするアクターリマインダーおよびスケジュール済みジョブ

以前は、リマインダー名やアクター ID に `|` や `@` などの文字が含まれていると、リマインダーの登録に失敗していました。また、厳格な DNS-1123 の文字セットに含まれないスケジュール済みジョブ名にも影響がありました。現在は、名前とアクター ID に大文字、`|`、`@`、`||` を使用できます。一方、`/`、`\`、`#`、`?`、制御文字、およびパス要素としての正確な文字列 `.` と `..` は引き続き使用できません。

> ## Actor reminders and jobs fail to register when their name or actor ID contains characters such as `|` or `@`
> ### Problem
> Registering an actor reminder through the Scheduler service failed when the reminder name, or the actor ID it belongs to, contained certain characters such as the pipe `|` or at sign `@`.
> The same characters are accepted when invoking actors and when saving actor state, so an actor that worked everywhere else could not have a reminder created for it.
> The error returned in this case was also misleading:
> a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
> It claimed only lowercase names were allowed even though uppercase names are in fact accepted, and it did not describe which characters were actually rejected.
> ### Impact
> You were affected if you used Scheduler-backed actor reminders (the default since 1.15) and your reminder names, actor IDs, or scheduled job names contained characters outside the strict DNS-1123 set, for example `|`, `@`, or uppercase letters.
> ### Root Cause
> The Scheduler composes each reminder or job into a single name of the form `actorreminder||<namespace>||<type>||<id>||<name>` (or `app||<namespace>||<appID>||<name>` for jobs), using `||` as an internal delimiter.
> Each `||`-delimited segment was then validated against Kubernetes' DNS-1123 subdomain rules, which only permit lowercase alphanumeric characters, `-`, and `.`.
> This was far stricter than the character set Dapr already accepts at its API edge, producing the inconsistency between actor invocation and reminder registration.
> Because the validator lowercased each segment before checking it, uppercase names passed in practice while the surfaced error still referred to lowercase-only RFC 1123 subdomains.
> ### Solution
> The Scheduler now validates names using the same policy Dapr applies at its API edge, so anything accepted for actor invocation can also be used for a reminder or job.
> Reminder names, job names, and actor identifiers may now contain any character except `/`, `\`, `#`, `?`, control characters (including the NUL byte), and the exact path sequences `.` and `..`.
> Uppercase letters and characters such as `|` and `@` are allowed, and `||` continues to be accepted within actor IDs and names.
> - [Actor reminders and jobs fail to register when their name or actor ID contains characters such as `|` or `@`](#actor-reminders-and-jobs-fail-to-register-when-their-name-or-actor-id-contains-characters-such-as--or-)

## その他の変更 (2)

- Scheduler の検証エラーで使用不可の文字を特定
- Scheduler の検証エラーにおける許可されない文字の明示

---

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