I am running Drupal 10.6.5 and it is prompting me to upgrade to 2.3.0 instead of 2.2.5.
I manually installed 2.2.5 via Composer but the prompt still appears and shows a yellow status on the Status Report page.
There are other plugins on the site which have Drupal 11 specific versions. These appear in the list of Available Updates under Reports, but they do not trigger a yellow status (see Gin Toolbar example).
| Comment | File | Size | Author |
|---|---|---|---|
| Screenshot 2026-03-20 at 5.29.18 AM.png | 87.21 KB | mr.white | |
| Screenshot 2026-03-20 at 5.33.56 AM.png | 96.52 KB | mr.white | |
| Screenshot 2026-03-20 at 5.33.39 AM.png | 87.09 KB | mr.white |
Comments
Comment #2
shank115 commentedThe warning occurs because the update system recommends the latest release within the same major branch, even if it requires a higher Drupal core version.
For now, you can ignore this if you're already on the latest compatible version (e.g. 2.2.5).
A proper fix would be to release Drupal 11-only changes in a new major branch (e.g. 3.x)
Comment #3
mr.white commentedThat makes sense.
It's not a big issue for me, but it does block updating to 2.2.5 via the Drupal web UI. The only update it offers is 2.3.0.
Updating manually via Composer seems to be the only way to go from 2.2.4 to 2.2.5.
Comment #4
gappleThat's understandably irritating for core to recommend an incompatible version.
It's sort of inverted since csp is a module for core, but semver allows minor version updates for dependency changes since csp's public API doesn't have any BC breaks.
The only changes from 2.2 to 2.3 are for compatibility with Drupal 12 that aren't BC compatible with Drupal 10, so there's no need to update to 2.3. 2.2 will still be maintained and any bug fixes will be backported while Drupal 10 is still supported.
New features (when ready) will go in 2.4+, which will also only support Drupal 11+ though.