The theme-skeleton compatibility has been pinned again

david · March 23, 2026, 10:19am

Thanks! (again )

Going forward, we’ll be using the new branch-based strategy described in RFC: A new versioning strategy for Discourse, so we won’t be running that automated .discourse-compatibility process again.

Revert "DEV: Pin version for Discourse < 2026.2.0-latest (#91)" by davidtaylorhq · Pull Request #97 · discourse/discourse-plugin-skeleton · GitHub
Revert "DEV: Pin version for Discourse < 2026.2.0-latest (#69)" by davidtaylorhq · Pull Request #77 · discourse/discourse-theme-skeleton · GitHub

Topic		Replies	Views
What is the purpose of the compatibility entry in the theme skeleton? Dev	7	123	September 7, 2025
Introducing .discourse-compatibility: pinned plugin/theme versions for older Discourse versions Announcements new-feature	18	4420	April 1, 2023
Pinning plugin and theme versions for older Discourse installs (.discourse-compatibility) Developer Guides	3	1215	September 15, 2025
Branching support for the theme deployment Support	6	887	August 16, 2021
Invalid hash in .discourse-compatiblity Bug gifs	3	428	July 15, 2023

The theme-skeleton compatibility has been pinned again

Related topics