summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLiam Cain <hi@liamca.in>2022-08-22 16:02:03 -0400
committerLiam Cain <hi@liamca.in>2022-08-22 16:02:03 -0400
commit42d72b4e594a356a0d1691f3817dcc42875feec6 (patch)
tree21bb87021daf0b784d12dd869cb9effd324f1a19
parente51bed6070138bfc4a4d88b006e204f582782635 (diff)
Build: Add version-bump script
-rw-r--r--version-bump.mjs26
1 files changed, 26 insertions, 0 deletions
diff --git a/version-bump.mjs b/version-bump.mjs
new file mode 100644
index 0000000..9d0e052
--- /dev/null
+++ b/version-bump.mjs
@@ -0,0 +1,26 @@
+/**
+ * This script makes it slightly easier to release new versions of your
+ * theme. If you are not using Github Releases with your theme, or
+ * you are not interested in automating the process, you can safely ignore
+ * this script.
+ *
+ * Usage: `$ npm run version`
+ *
+ * This script will automatically add a new entry to the versions.json file for
+ * the current version of your theme.
+ */
+
+import { readFileSync, writeFileSync } from "fs";
+
+const targetVersion = process.env.npm_package_version;
+
+// read minAppVersion from manifest.json and bump version to target version
+let manifest = JSON.parse(readFileSync("manifest.json", "utf8"));
+const { minAppVersion } = manifest;
+manifest.version = targetVersion;
+writeFileSync("manifest.json", JSON.stringify(manifest, null, "\t"));
+
+// update versions.json with target version and minAppVersion from manifest.json
+let versions = JSON.parse(readFileSync("versions.json", "utf8"));
+versions[targetVersion] = minAppVersion;
+writeFileSync("versions.json", JSON.stringify(versions, null, "\t"));