# Theme (component)s do not look at .discourse-compatibility on update

**URL:** https://meta.discourse.org/t/theme-component-s-do-not-look-at-discourse-compatibility-on-update/400248
**Category:** Bug
**Created:** [April 8, 2026, 6:28pm UTC](https://meta.discourse.org/t/theme-component-s-do-not-look-at-discourse-compatibility-on-update/400248 "2026-04-08T18:28:51Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [April 8, 2026, 6:28pm UTC](https://meta.discourse.org/t/theme-component-s-do-not-look-at-discourse-compatibility-on-update/400248/1 "2026-04-08T18:28:51Z")

</div>

A theme (component) honors `.discourse-compatibility` when it is installed, which is good 👍

However, when `.discourse-compatibility` is [updated](https://meta.discourse.org/t/topic-list-previews-tlp/209973/730) **after** the theme component has been installed **and updated beyond the target version** , the version is not rolled back on the next update of the theme component.

The only way to recover is to:

- copy the settings and store them in a safe place
- remove the theme component
- reinstall the theme component
- paste the settings

Which is doable, IF you know what is going on. But the regular “press the update button and see your problem go away” does not help you.

Desired: a theme component would inspect `.discourse-compatibility` on every update and roll back if necessary .

Yes, I know that can have nasty side effects but I’m convinced that those are less serious than not rolling back.

---

_[View the full topic](https://meta.discourse.org/t/theme-component-s-do-not-look-at-discourse-compatibility-on-update/400248)._