cloudflare/workers-sdk create-cloudflare@2.72.7 ↗
11 Sept, 23:22 JST
Patch release create-cloudflare@2.72.7. New projects now default to a compatibility date of 2026-09-11, tracking the pinned workerd 1.20260911.1 release.
Editor’s take
When a default compatibility date moves, template-built projects inherit behavior nobody chose. Tying that date to a pinned workerd release concentrates runtime drift into one value. It is the office printer switching paper size: output shifts before anyone reads a setting. Most teams never notice.
Read the evidence
- Who it affects
- Developers about to scaffold a new Cloudflare Workers project
- What remains unknown
- Whether existing projects are affected, what changed inside workerd 1.20260911.1, and runtime impact details are missing.
- Original source
- ### Patch Changes - [#15604](https://github.com/cloudflare/workers-sdk/pull/15604) [`9109a76`](https://github.com/cloudflare/workers-sdk/commit/9109a767a47defa3e060632b3e39f918ed628c27) Thanks [@dom96](https://github.com/dom96)! - Update the default compatibility date for newly created projects to 2026-09-11 The default compatibility date tracks the pinned `workerd` release, which was bumped to `1.20260911.1`. Releasing C3 ships the updated date to `npm create cloudflare` users, since it is bundled into the published package.