Release prep: bump version to 0.13.1, pypowerwall 0.22.2

RELEASE.md

@@ -2,7 +2,10 @@
 
 ## Version History
 
-### [0.13.1] - Upcoming
+### [0.13.1] - 2026-10-27
+
+Battery dispatch becomes a separate opt-in, with a clear "use at your own risk"
+warning, plus pypowerwall 0.22.2. Read **Changed** if you use battery dispatch.
 
 **Changed:**
 - **Battery dispatch is now opt-in: `PW_BATTERY_DISPATCH=yes`.** This is a
@@ -14,19 +17,23 @@
   or the grid. `POST /control/resume` works without it, so turning it off never
   strands a running dispatch. The server logs a warning at startup when it's
   on, and `/stats` reports it under `config`. (#185)
+- **pypowerwall upgraded to 0.22.2** (from 0.22.1; `requirements.txt` pin and
+  `pyproject.toml` minimum). Each accepted battery dispatch is now logged at
+  WARNING (action, watts, duration), and the library documents dispatch as use
+  at your own risk (jasonacox/pypowerwall#446).
 
 **Added:**
 - **Battery dispatch safeguards in the Console.** Every dispatch (charge,
   discharge or 0 W) asks for confirmation, showing its risks, and the result
-  says when it is expected to end. Console durations
-  are capped at 4 hours (the API still accepts up to 86400 seconds). The panel
-  shows one caution line, with the full risks behind an info icon. (#185)
+  says when it is expected to end. Console durations are capped at 4 hours
+  (the API still accepts up to 86400 seconds). The panel shows one caution
+  line, with the full risks behind an info icon. (#185)
+- **"Use at your own risk" warning** for battery dispatch in README and API.md. (#185)
 
 **Fixed:**
 - **Battery dispatch success needs the gateway's acknowledgement for that
   command** (matching power and duration, or `resume_battery_operation:
   true`). Any other non-error reply was reported as success. (#185)
-- **"Use at your own risk" warning** for battery dispatch in README and API.md. (#185)
 
 ### [0.13.0] - 2026-10-26
 

app/config.py

@@ -257,7 +257,7 @@ def _scalar_kind(annotation):
 
 
 # Server version
-SERVER_VERSION = "0.13.0"
+SERVER_VERSION = "0.13.1"
 
 # MQTT control bitmask values for MQTT_CONTROLS (bits only, no names).
 # Default 0 keeps MQTT monitoring-only, exactly as before controls existed.

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pypowerwall-server"
-version = "0.13.0"  # Also defined in app/config.py as SERVER_VERSION
+version = "0.13.1"  # Also defined in app/config.py as SERVER_VERSION
 description = "A high-performance FastAPI-based server for monitoring and managing Tesla Powerwall systems"
 readme = "README.md"
 authors = [
@@ -31,7 +31,7 @@ dependencies = [
     "uvicorn[standard]>=0.29.0",
     "pydantic>=2.11.0",
     "pydantic-settings>=2.9.0",
-    "pypowerwall>=0.22.1",
+    "pypowerwall>=0.22.2",
     "websockets>=13.1",
     "psutil>=6.1.0",
     "beautifulsoup4>=4.12.0",

requirements.txt

@@ -2,7 +2,7 @@ fastapi==0.115.12
 uvicorn[standard]==0.29.0
 pydantic==2.11.3
 pydantic-settings==2.9.1
-pypowerwall==0.22.1
+pypowerwall==0.22.2
 websockets==13.1
 psutil==6.1.1
 beautifulsoup4==4.12.3