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.

Wat is het doel van de compatibiliteitsvermelding in het thema-skelet?

Ontwikkelaar

david (David Taylor) 12 juni 2025 om 22:53 4

Now removed.

Topic		Antwoorden	Weergaven
The theme-skeleton compatibility has been pinned again Development	1	72	23 maart 2026
Overly restrictive compatibility value for brand header component Support brand-header	2	86	20 augustus 2025
Introducing .discourse-compatibility: pinned plugin/theme versions for older Discourse versions Announcements new-feature	18	4516	1 april 2023
Invalid hash in .discourse-compatiblity Bug gifs	2	454	12 juli 2023
Pinning plugin and theme versions for older Discourse installs (d-compat branches) Developer Guides	4	1353	27 mei 2026

Wat is het doel van de compatibiliteitsvermelding in het thema-skelet?

Gerelateerde topics