Continuing the discussion from What is the purpose of the compatibility entry in the theme skeleton?:
It has happened again:
Is there any way to prevent this somehow?
Continuing the discussion from What is the purpose of the compatibility entry in the theme skeleton?:
It has happened again:
Is there any way to prevent this somehow?
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.