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.

ما الغرض من إدخال التوافق في هيكل السمة؟

مطور

david (David Taylor) 12 يونيو 2025، 5:21م 3

شكرًا على التنبيه - لم يكن يجب علينا دمج ذلك في الهيكل الافتراضي. سيتم التراجع عنه

The theme-skeleton compatibility has been pinned again

الموضوع		الردود	مرات العرض
The theme-skeleton compatibility has been pinned again Development	1	78	23 مارس 2026
Overly restrictive compatibility value for brand header component Support brand-header	2	97	20 أغسطس 2025
Invalid version list in discourse themes Self-hosting	5	92	17 يوليو 2026
Introducing .discourse-compatibility: pinned plugin/theme versions for older Discourse versions Announcements new-feature	18	4571	1 أبريل 2023
Invalid hash in .discourse-compatiblity Bug gifs	2	457	12 يوليو 2023

ما الغرض من إدخال التوافق في هيكل السمة؟

الموضوعات ذات الصلة