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 # # Exampl…

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 Req…

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?

Dev

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

Now removed.

2 Likes

Topic		Replies	Views
The theme-skeleton compatibility has been pinned again Dev	1	48	March 23, 2026
Overly restrictive compatibility value for brand header component Support brand-header	3	56	September 19, 2025
Pinning plugin and theme versions for older Discourse installs (.discourse-compatibility) Developer Guides	3	1215	September 15, 2025
Introducing .discourse-compatibility: pinned plugin/theme versions for older Discourse versions Announcements new-feature	18	4420	April 1, 2023
Invalid hash in .discourse-compatiblity Bug gifs	3	428	July 15, 2023

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

Related topics