feat(ci): setup

.changes/config.json

@@ -0,0 +1,26 @@
+{
+  "gitSiteUrl": "https://www.github.com/tauri-apps/tauri-plugin-websocket/",
+  "pkgManagers": {
+    "rust": {
+      "version": true,
+      "publish": true,
+      "getPublishedVersion": "cargo search ${ pkg.pkg } --limit 1 | sed -nE 's/^[^\"]*\"//; s/\".*//1p' -"
+    },
+    "javascript": {
+      "version": true,
+      "publish": true,
+      "getPublishedVersion": "npm view ${ pkgFile.pkg.name } version"
+    }
+  },
+  "packages": {
+    "tauri-plugin-websocket-api": {
+      "path": "./typescript",
+      "manager": "javascript",
+      "dependencies": ["tauri-plugin-websocket"]
+    },
+    "tauri-plugin-websocket": {
+      "path": ".",
+      "manager": "rust"
+    }
+  }
+}

.changes/initial-release.md

@@ -0,0 +1,6 @@
+---
+"tauri-plugin-websocket-api": patch
+"tauri-plugin-websocket": patch
+---
+
+Initial release.

.changes/readme.md

@@ -0,0 +1,17 @@
+# Changes
+##### via https://github.com/jbolda/covector
+
+As you create PRs and make changes that require a version bump, please add a new markdown file in this folder. You do not note the version *number*, but rather the type of bump that you expect: major, minor, or patch. The filename is not important, as long as it is a `.md`, but we recommend it represents the overall change for our sanity.
+
+When you select the version bump required, you do *not* need to consider depedencies. Only note the package with the actual change, and any packages that depend on that package will be bumped automatically in the process.
+
+Use the following format:
+```md
+---
+"tauri-plugin-websocket": minor
+"tauri-plugin-websocket-api": minor
+---
+
+Change summary goes here
+
+```