Hash non valido in .discourse-compatiblity

nat · 12 Luglio 2023, 7:52am

Ho testato questa correzione localmente e dovrebbe essere risolta qui (la PR fornisce una descrizione del problema):

github.com/discourse/discourse-gifs

DEV: Use theme's commit sha to match against 'current' core version -1

main ← update-discourse-compat

opened 07:47AM - 12 Jul 23 UTC

nattsw

+1 -1

`.discourse-compatibility` can be quite confusing, but the gist of it is: ✔️ `…<discourse-core-version>: theme-sha` ❌ `<discourse-core-version>: discourse-core-sha` Scenario: Discourse core current version is `3.1.0.beta5`, and I make a commit to core that defines a new API. In my plugin / theme, I make a commit that uses that API. That commit's sha is `eb3ec48c`. The values that go into the compat file is: `3.1.0.beta5` `-1`: `eb3ec48c` `-1` therefore `3.1.0.beta4: c48cf8812c3d` Related: - Solves https://meta.discourse.org/t/invalid-hash-in-discourse-compatiblity/270865/2 - https://github.com/discourse/discourse-gifs/pull/38 - https://github.com/discourse/discourse/pull/21783

Argomento		Risposte	Visualizzazioni
Invalid version list in discourse themes Self-hosting	5	184	Luglio 17, 2026
Introducing .discourse-compatibility: pinned plugin/theme versions for older Discourse versions Announcements new-feature	18	4738	Aprile 1, 2023
Overly restrictive compatibility value for brand header component Support brand-header	2	152	Agosto 20, 2025
Pinning plugin and theme versions for older Discourse installs (d-compat branches) Developer Guides	6	1707	Luglio 17, 2026
One of your themes or plugins needs updating for compatibility with upcoming Discourse core changes Development	2	285	Luglio 6, 2024

Hash non valido in .discourse-compatiblity

Argomenti correlati