khoj/versions.json

{
	"0.2.1": "0.15.0",
	"0.2.5": "0.15.0",
	"0.2.6": "0.15.0",
	"0.3.0": "0.15.0",
	"0.4.0": "0.15.0",
	"0.5.0": "0.15.0",
	"0.6.0": "0.15.0",
	"0.6.1": "0.15.0",
	"0.6.2": "0.15.0"
}
Add manifest.json, versions.json of Obsidian plugin to project root - Obsidian provides limited support for plugins in larger repositories. Currently, it does not have a way to specify the directory of a plugin So it expects the plugins `manifest.json' and `versions.json' to be at project root - While this unnecessarily litters the codebase. It is the (current) required tradeoff for keeping the core plugins in a mono repo 2023-01-04 20:31:11 +01:00			`{`
Release Khoj version 0.5.0 2023-03-27 22:34:07 +02:00			`"0.2.1": "0.15.0",`
			`"0.2.5": "0.15.0",`
			`"0.2.6": "0.15.0",`
			`"0.3.0": "0.15.0",`
			`"0.4.0": "0.15.0",`
Release Khoj version 0.6.0 Upload styles.css via release workflow 2023-03-31 12:50:28 +02:00			`"0.5.0": "0.15.0",`
Release Khoj version 0.6.1 2023-04-17 16:46:28 +02:00			`"0.6.0": "0.15.0",`
Release Khoj version 0.6.2 2023-05-17 16:34:20 +02:00			`"0.6.1": "0.15.0",`
			`"0.6.2": "0.15.0"`
Add manifest.json, versions.json of Obsidian plugin to project root - Obsidian provides limited support for plugins in larger repositories. Currently, it does not have a way to specify the directory of a plugin So it expects the plugins `manifest.json' and `versions.json' to be at project root - While this unnecessarily litters the codebase. It is the (current) required tradeoff for keeping the core plugins in a mono repo 2023-01-04 20:31:11 +01:00			`}`