This was added last week: .discourse-compatibility main # Map Discourse core versions to a specific commit of this theme. # More info: https://meta.discourse.org/t/how-to-use-discourse-compatibility-files/260786 # # Format: # < core-version: commit-hash of this theme # # Example: # < 2026.2.0-latest: abcde12345 Can someone explain the purpose? In principle, I understand what the file is used for, as explained in the documentation. But I don’t quite understand the point that this is now part of the template for all themes and theme components.

Just a heads-up, a compatibility entry has been added again: .discourse-compatibility 9d0a95737 < 3.6.0.beta1-dev: 38c281a9907b82f8af2a3a63e53801653fb3097c Edit: PR to remove it DEV: Remove the discourse-compatibility entry by moin-Jana · Pull Request #58 · discourse/discourse-theme-skeleton · GitHub :check_mark: merged

Thanks for the heads-up - we shouldn’t have merged that into the default skeleton. Will get it reverted :eyes:

In hindsight, it makes sense to have that file present, with likely the oldest supported version or a comment somewhere that leads to the documentation for compatibility file. it is a skeleton and compatibility file plays an important role these days.

What is the purpose of the compatibility entry in the theme skeleton?

Development

david (David Taylor) June 12, 2025, 10:53pm 4

Now removed.

Topic		Replies	Views
The theme-skeleton compatibility has been pinned again Development	1	141	March 23, 2026
Overly restrictive compatibility value for brand header component Product Support brand-header	2	181	August 20, 2025
Invalid version list in discourse themes Self-hosting	5	238	July 17, 2026
Introducing .discourse-compatibility: pinned plugin/theme versions for older Discourse versions Announcements new-feature	18	4924	April 1, 2023
Invalid hash in .discourse-compatiblity Bug gifs	2	516	July 12, 2023

What is the purpose of the compatibility entry in the theme skeleton?

Related topics