Use manual publishing for tauri crate

Author: simolus3

.github/workflows/release-tauri-crate.yml

@@ -1,8 +1,6 @@
-name: release
+name: Release tauri plugin crate
 on:
-  push:
-    tags:
-      - tauri-plugin-powersync@[0-9]+.[0-9]+.[0-9]+
+  workflow_dispatch:
 
 jobs:
   publish_crates_io:
@@ -14,8 +12,8 @@ jobs:
       - uses: rust-lang/crates-io-auth-action@v1
         id: auth
 
-      - name: Publish powersync crate
+      - name: Publish tauri-plugin-powersync crate
         run: cargo publish
-        working-directory: powersync
+        working-directory: packages/tauri
         env:
           CARGO_REGISTRY_TOKEN: ${{ steps.auth.outputs.token }}

packages/tauri/releasing.md

@@ -0,0 +1,7 @@
+The `@powersync/tauri-plugin` npm package is versioned through changesets.
+
+The version of the `tauri-plugin-powersync` crate is also managed by changesets,
+but we can't reliably publish to crates.io through that automation.
+
+If the Rust crate should get published, manually run the "Release tauri plugin crate"
+workflow on a `tauri-plugin-powersync@<version>` tag created by changesets.