# Theme component update always installs old version (via rake or manually) (solved)

**URL:** https://meta.discourse.org/t/theme-component-update-always-installs-old-version-via-rake-or-manually-solved/388241
**Category:** Support
**Created:** [November 12, 2025, 11:57am UTC](https://meta.discourse.org/t/theme-component-update-always-installs-old-version-via-rake-or-manually-solved/388241 "2025-11-12T11:57:22Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [November 12, 2025, 12:30pm UTC](https://meta.discourse.org/t/theme-component-update-always-installs-old-version-via-rake-or-manually-solved/388241/2 "2025-11-12T12:30:20Z")

</div>

The compatibility file installs a specific version for Discourse installs below 3.6.

> <https://github.com/toad/discourse-new-topic-button-theme-component/blob/main/.discourse-compatibility#L1>

> [@Pinning plugin and theme versions for older Discourse installs (d-compat branches)](https://meta.discourse.org/t/pinning-plugin-and-theme-versions-for-older-discourse-installs-discourse-compatibility/272665):
>
> open_book Background Theme and plugin developers generally want to target the latest release of Discourse, without worrying about backwards compatibility. But sites running older Discourse releases still need a version of the theme/plugin that works for them. To bridge that gap, Discourse can be told to check out an older ‘pinned’ version of the theme/plugin. There are two mechanisms for this, checked in order: d-compat/\<YYYY\>.\<M\> git branches in the theme/plugin repository (the primary met…

---

_[View the full topic](https://meta.discourse.org/t/theme-component-update-always-installs-old-version-via-rake-or-manually-solved/388241)._