Clean up release guide

Author: mugikhan

.github/workflows/publish.yml

@@ -3,8 +3,8 @@ on:
   push:
     tags:
       - "powersync-v[0-9]+.[0-9]+.[0-9]+"
-      - "powersync_attachments_helper-v[0-9]+.[0-9]+.[0-9]+"
-      - "powersync_flutter_libs-v[0-9]+.[0-9]+.[0-9]+"
+      - "powersync_attachments_helper-v[0-9]+.[0-9]+.[0-9]+*"
+      - "powersync_flutter_libs-v[0-9]+.[0-9]+.[0-9]+*"
   workflow_dispatch:
 
 jobs:

RELEASING.md

@@ -9,11 +9,11 @@ melos version
 if melos does not pick up changes or does not bump the version correctly, you can manually version the packages using
 
 ```
-melos version -V ${PACKAGE_NAME}:m.m.p
+melos version -V ${PACKAGE_NAME}:M.M.P
 for e.g melos version -V powersync:1.6.3
 ```
 
-This will create a tag in the format of ${PACKAGE_NAME}-vm.m.p
+This will create a tag for all packages updated in the format of ${PACKAGE_NAME}-vM.M.P
 
 ```
 e.g powersync-v1.6.4, powersync_attachments_helper-v0.6.3+1, etc.
@@ -24,3 +24,5 @@ e.g powersync-v1.6.4, powersync_attachments_helper-v0.6.3+1, etc.
 ```
 git push --follow-tags
 ```
+
+The pushed tags will also create a draft github release for the powersync web worker. The worker needs to be manually published in the GitHub [releases](https://github.com/powersync-ja/powersync.dart/releases).