agents@0.11.7
cloudflare/agentsagents@0.11.7Apr 28, 2026by github-actions[bot]
AI Summary
This is a patch release (0.11.7) that bumps the `partyserver` peer dependency to ^0.5.4 to fix a bug where fresh 0.5.x Durable Objects with compatibility_date older than 2026-03-15 could lose `this.name` on alarm wake. The fix adds a defensive one-time `__ps_name` write on first fetch to restore the legacy fallback behavior.
Key Highlights
- Bumped `partyserver` peer dependency to ^0.5.4
- Fixed bug where Durable Objects with pre-2026-03-15 compatibility_date could lose `this.name` on alarm wake
- Issue caused by missing `ctx.id.name` propagation in older runtimes and removal of `__ps_name` legacy fallback in 0.5.x
- Fix is defensive and idempotent - writes `__ps_name` once on first fetch to restore safety net
- Affects projects with pre-cutoff compatibility_date whose DOs schedule alarms (including Think's `_chatRecoveryContinue`)
Full Release Notes
### Patch Changes - [#1405](https://github.com/cloudflare/agents/pull/1405) [`03620a6`](https://github.com/cloudflare/agents/commit/03620a671b0c29ed4f99c82a4cd0d51c7fec7fa3) Thanks [@threepointone](https://github.com/threepointone)! - Bump `partyserver` peer dependency to `^0.5.4`. 0.5.4 closes [`cloudflare/partykit#390`](https://github.com/cloudflare/partykit/issues/390): fresh 0.5.x DOs with `compatibility_date` older than 2026-03-15 could lose `this.name` on alarm wake (no `ctx.id.name` propagation in older runtimes, and 0.5.x had stopped writing the `__ps_name` legacy fallback record). The fix is a defensive one-time `__ps_name` write on first fetch — idempotent, restores the safety net pre-0.5.x had. Affects any project on a pre-cutoff `compatibility_date` whose DOs schedule alarms (which includes Think's `_chatRecoveryContinue`).