# CPalius CMF 2.2.17

**Released:** 2026-09-25 · **Channel:** stable · **Critical:** no

Turkish: [2.2.17-tr.md](2.2.17-tr.md)

No functional change. This release exists to answer one question: does the crash that 2.2.11 through 2.2.16 chased ("stale compiled container", `ModuleListenerGuard...Service.php` missing) still occur when *installing* an update, given that the code applying the update is now itself already 2.2.16?

## Why this release exists

PHP does not reload a class's file mid-request just because an update overwrote it on disk. The request that installs a given release always runs on whatever code was already loaded into memory when that request started — which is the *previous* version, not the one being installed. If a site's last successful update landed on anything before 2.2.16, the request that performed that update was still running pre-2.2.16 logic, including whichever forced-purge behavior that version still had. That is a one-time transitional effect of self-updating a live PHP process, not a bug in the version being installed.

2.2.17 tests that explanation directly. Every file in this release is byte-identical to 2.2.16 except the version constant. If updating from 2.2.16 to 2.2.17 completes cleanly, the crash was the known one-time transitional effect and 2.2.16's fix holds for every update from here on. If it recurs even on this transition, the cause is not the one 2.2.16 fixed, and needs a different diagnosis.

## What's in this release

Nothing. `CpVersion::VERSION` only.