From 378350152229ea41870fb627340f7e6e2264e5e6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Camille=20Lou=C3=A9doc-Eyri=C3=A8s?=
 <camille.eyries@gmail.com>
Date: Fri, 24 Jun 2022 19:49:39 +0000
Subject: [PATCH] chore: release 0.0.2

---
 DEV_README.md | 9 +++++++++
 manifest.json | 2 +-
 versions.json | 1 +
 3 files changed, 11 insertions(+), 1 deletion(-)
 create mode 100644 DEV_README.md

diff --git a/DEV_README.md b/DEV_README.md
new file mode 100644
index 0000000..e492469
--- /dev/null
+++ b/DEV_README.md
@@ -0,0 +1,9 @@
+## Developer's README.md
+
+### Releasing a new version
+
+1. Update your manifest.json with your new version number, such as 1.0.1, and the minimum Obsidian version required for your latest release.
+2. Update your versions.json file with "new-plugin-version": "minimum-obsidian-version" so older versions of Obsidian can download an older version of your plugin that's compatible.
+3. Create new GitHub release using your new version number as the "Tag version". Use the exact version number, don't include a prefix v. See here for an example: https://github.com/obsidianmd/obsidian-sample-plugin/releases
+4. Upload the files manifest.json, main.js, styles.css as binary attachments. Note: The manifest.json file must be in two places, first the root path of your repository and also in the release.
+   Publish the release.
diff --git a/manifest.json b/manifest.json
index f93e80f..6fc883e 100644
--- a/manifest.json
+++ b/manifest.json
@@ -1,7 +1,7 @@
 {
 	"id": "postgresql-obsidian",
 	"name": "PostgreSQL Obsidian",
-	"version": "0.0.1",
+	"version": "0.0.2",
 	"minAppVersion": "0.12.0",
 	"description": "An Obsidian plugin to upload your notes' metadata to your database.",
 	"author": "clouedoc",
diff --git a/versions.json b/versions.json
index 07e4cbd..c935202 100644
--- a/versions.json
+++ b/versions.json
@@ -1,3 +1,4 @@
 {
+	"0.0.2": "0.9.7",
 	"0.0.1": "0.9.7"
 }