Prepare release 0.2.11 for distribution

Update all package manifests to the same release version before tagging and publishing desktop artifacts.

Constraint: publish.sh owns version synchronization across package.json, tauri.conf.json, Cargo.toml, and Cargo.lock.

Rejected: Manual version edits | The release script keeps manifest updates atomic.

Confidence: high

Scope-risk: narrow

Directive: Keep release metadata aligned before creating tags.

Tested: publish.sh updated package.json, src-tauri/tauri.conf.json, src-tauri/Cargo.toml, and src-tauri/Cargo.lock.

Not-tested: GitHub Actions release workflow before tag push.

Author: dickwu

package.json

@@ -1,7 +1,7 @@
 {
   "name": "Cloudflare R2 Client",
   "private": true,
-  "version": "0.2.10",
+  "version": "0.2.11",
   "scripts": {
     "dev": "next dev --turbopack -p 3000",
     "build": "next build",

src-tauri/Cargo.lock

@@ -3,7 +3,7 @@ members = [".", "crates/range-dl"]
 
 [package]
 name = "r2"
-version = "0.2.10"
+version = "0.2.11"
 description = "A desktop application for managing Cloudflare R2 storage buckets."
 authors = ["Peilin Wu"]
 edition = "2021"

src-tauri/Cargo.toml

@@ -1,7 +1,7 @@
 {
   "$schema": "https://schema.tauri.app/config/2",
   "productName": "r2",
-  "version": "0.2.10",
+  "version": "0.2.11",
   "identifier": "com.lifefarmer.r2",
   "build": {
     "beforeDevCommand": "bun run dev",