# Featured Topics

**URL:** https://meta.discourse.org/t/featured-topics/217580
**Category:** Theme component
**Created:** [February 8, 2022, 9:38pm UTC](https://meta.discourse.org/t/featured-topics/217580 "2022-02-08T21:38:36Z")
**Posts on this page:** 1
**Showing post:** 77

<div class="post-metadata">

### Author: ![manuel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/manuel/32/468169_2.png) [@manuel](https://meta.discourse.org/u/manuel)
#### Post date: [September 9, 2026, 11:00am UTC](https://meta.discourse.org/t/featured-topics/217580/77 "2026-09-09T11:00:15Z")

</div>

Updated and set minimum version to `2026.7.999`.

What apparently happens is that any suffix is treated as a pre-release, so `2026.8.0-latest.1` sorts below `2026.8.0.`

I think that’s quite unintuitive and posted a bug report:

> [@Minimum\_discourse\_version fails its check on -latest builds (e.g. 2026.8.0-latest.1)](https://meta.discourse.org/t/minimum-discourse-version-fails-its-check-on-latest-builds-e-g-2026-8-0-latest-1/411985):
>
> Themes/components on the default latest channel get auto-disabled, and theme authors must use unintuitive workarounds. Ran into this here: [Featured Topics - #76 by cogdog](https://meta.discourse.org/t/featured-topics/217580/76) It’s quite unintuitive that all minimum versions need to use a format like xxx.x.999 below the current version they should actually match. Platform Self-hosted Discourse on the latest branch Discourse version: 2026.8.0-latest.1 Affects: theme/theme-component authoring (about.json metadata) and theme compatibility checks Des…

Edit: Learned on the above topic that current best practice is to not use these values at all, but use the compatibility branches. The current setup should work, but when I find time I’ll update the component to use branches.

---

_[View the full topic](https://meta.discourse.org/t/featured-topics/217580)._