# Overly restrictive compatibility value for brand header component
**URL:** https://meta.discourse.org/t/overly-restrictive-compatibility-value-for-brand-header-component/379434
**Category:** Support
**Tags:** brand-header
**Created:** [August 20, 2025, 8:46am UTC](https://meta.discourse.org/t/overly-restrictive-compatibility-value-for-brand-header-component/379434 "2025-08-20T08:46:26Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@simonk](https://meta.discourse.org/u/simonk)
#### Post date: [August 20, 2025, 8:46am UTC](https://meta.discourse.org/t/overly-restrictive-compatibility-value-for-brand-header-component/379434/1 "2025-08-20T08:46:26Z")
I’ve just upgraded to 3.5.0.beta9 (`3cac943266`) and am receiving an admin notice:
> **[Admin Notice]** Theme ‘Brand Header Theme Component’ contains code which needs updating. (id:discourse.widgets-end-of-life) ([_learn more_](https://meta.discourse.org/t/375332/1))
As far as I can tell, the component has been updated:
[https://github.com/discourse/discourse-brand-header/commit/f002a9350b9ca1cdb720d9d0b9da1424e2abe6a3](https://github.com/discourse/discourse-brand-header/commit/f002a9350b9ca1cdb720d9d0b9da1424e2abe6a3)
…but the update cannot be installed on 3.5.0.beta9 because the `.discourse-compatibility` file contains this line:
`< 3.5.0.beta9-dev: 6fd676ea4e9cd7305d03df93bd6ce99961e4ff17`
(where `6fd676ea4e9c...` is the commit **before** the fix)
Is 3.5.0.beta9 really not able to use the fixed code?
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [August 20, 2025, 8:48am UTC](https://meta.discourse.org/t/overly-restrictive-compatibility-value-for-brand-header-component/379434/2 "2025-08-20T08:48:30Z")
> [@simonk](#):
>
> …but the update cannot be installed on 3.5.0.beta9 because the `.discourse-compatibility` file contains this line:
>
> `< 3.5.0.beta9-dev: 6fd676ea4e9cd7305d03df93bd6ce99961e4ff17`
It should be possible to install the latest version. The line in the compatibilty file means “Discourse versions **before** 3.5.0.beta9-dev must use the old version of the theme”. Since you’re on beta9, you should be able to use the latest version of the theme.
What are you seeing when you try to update?
---
### Author:  [@simonk](https://meta.discourse.org/u/simonk)
#### Post date: [August 20, 2025, 8:54am UTC](https://meta.discourse.org/t/overly-restrictive-compatibility-value-for-brand-header-component/379434/3 "2025-08-20T08:54:08Z")
I’m so sorry - I noticed the problem yesterday when I first upgraded, but I waited until today to report it. At the time, the dashboard wasn’t showing any available updates for the component and I jumped to the conclusion that it was because of the compatibility file. In fact it was probably just that the background check-for-updates task hadn’t run yet 🤦♂️.
I have now updated the component and everything is fine. Sorry for wasting your time!
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [September 19, 2025, 8:54am UTC](https://meta.discourse.org/t/overly-restrictive-compatibility-value-for-brand-header-component/379434/4 "2025-09-19T08:54:19Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.