# Minimum\_discourse\_version fails its check on -latest builds (e.g. 2026.8.0-latest.1)

**URL:** https://meta.discourse.org/t/minimum-discourse-version-fails-its-check-on-latest-builds-e-g-2026-8-0-latest-1/411985
**Category:** Bug
**Created:** [9 בספטמבר,‏ 2026,‏ 10:55am UTC](https://meta.discourse.org/t/minimum-discourse-version-fails-its-check-on-latest-builds-e-g-2026-8-0-latest-1/411985 "2026-09-09T10:55:49Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [9 בספטמבר,‏ 2026,‏ 11:49am UTC](https://meta.discourse.org/t/minimum-discourse-version-fails-its-check-on-latest-builds-e-g-2026-8-0-latest-1/411985/7 "2026-09-09T11:49:21Z")

</div>

> [@david](#):
>
> We should fix that. Theme authors should be able to do:
> 
> ```plaintext
> minimumDiscourseVersion: "2026.8.0-latest"
> 
> ```

> <https://github.com/discourse/discourse/pull/43459>
>
> Discourse builds are versioned as \`2026.8.0-latest\` and \`2026.8.0-latest.1\` betw…een releases, but the \`about.json\` validation for \`minimum\_discourse\_version\` and \`maximum\_discourse\_version\` only accepted \`X.Y.Z\` and \`X.Y.Z.betaN\`. Gem::Version treats \`-latest\` as a pre-release, so a theme that needs \`2026.8.0\` was disabled on \`2026.8.0-latest.1\`, and authors could not express the intended constraint \`2026.8.0-latest\` because the import rejected it.
> 
> \- \`Discourse::VERSION\_REGEXP\` now allows \`-latest\` and \`-latest.N\` suffixes.
> \- Add specs for the regexp, for \`has\_needed\_version?\` ordering of \`-latest\` builds, and for the \`RemoteTheme\` validation.
> 
> See https://meta.discourse.org/t/411985

---

_[View the full topic](https://meta.discourse.org/t/minimum-discourse-version-fails-its-check-on-latest-builds-e-g-2026-8-0-latest-1/411985)._