- Issue created by @leksat
- Status changed to Closed: works as designed
25 days ago 11:07am 20 June 2025 - 🇦🇺Australia dpi Perth, Australia
The update page makes it look like Drupal is complaining or showing errors about the version you have vs what is available.
This is certainly a UX issue.
The version combination you have, of ST and core are not an issue.
What I read the Drupal report as is similar to `composer outdated --direct`, in which it it spells out you are not on the latest. But it should be smarter about communicating that.
Perhaps the problem lies with core's interpretation that a major version of a contrib is whether new core compat comes in. Whereas ST, and many other projects outside of the Drupal ecosystem, will include new major dependency changes in a minor version.
In any case this is not a problem with ST itself, and I have no intention of changing my release model to a new major for each Drupal core major.
