Minimum_discourse_version fails its check on -latest builds (e.g. 2026.8.0-latest.1)

[david (David Taylor)]

@manuel

Because apparently a feature landed in 2026.5.0 and to match that I need to put 2026.4.999?

In the past, yes, so there are some old themes/plugins still doing that (and I guess humans/robots are continuing to copy the legacy pattern).

But nowadays you can use < or > indicators on the left-hand-side of the compatibility file. So you can do

<2026.7.0-latest: 93b5b22

But also, we try to avoid using the compatibility file for anything these days. Instead we rely on the automatic d-compat/* branches to take care of compatibility with past versions.

Docs on both old and new patterns are here:

Pinning plugin and theme versions for older Discourse installs (d-compat branches)

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…