[jasonacox]

Release prep for 0.13.1: bumps SERVER_VERSION and the pyproject.toml version, pins pypowerwall 0.22.2 (the requirements.txt pin and pyproject.toml minimum), and dates the release notes with a summary.

What's in 0.13.1:

• Battery dispatch is opt-in: PW_BATTERY_DISPATCH=yes (feat(control): battery dispatch is opt-in (PW_BATTERY_DISPATCH), use at your own risk #185). This is a behavior change from 0.13.0: with only PW_CONTROL_SECRET set, the panel is hidden and POST /control/dispatch returns 403. Resume always works. There's a "use at your own risk" warning in the docs, a startup warning, and /stats reports the setting.
• Console safeguards (feat(control): battery dispatch is opt-in (PW_BATTERY_DISPATCH), use at your own risk #185): every dispatch asks for confirmation, durations are capped at 4 hours, and the panel has one caution line with an ⓘ popup.
• Fix (feat(control): battery dispatch is opt-in (PW_BATTERY_DISPATCH), use at your own risk #185): success needs the gateway's acknowledgement for that command.
• pypowerwall 0.22.2: each accepted dispatch is logged at WARNING, and the library documents dispatch as use at your own risk (docs(v1r): battery dispatch is use at your own risk; log each accepted dispatch pypowerwall#446).

Checks: pytest 1163 passed against the pinned pypowerwall 0.22.2 (fresh venv from requirements.txt). ./upload-pypi.sh --dry-run builds cleanly.

After merge: upload to PyPI, build and push Docker jasonacox/pypowerwall-server:0.13.1 and :latest, and tag v0.13.1.

🤖 Generated with Claude Code

[Copilot]

🟢 Approval recommended

No active review issues block the 0.13.1 release preparation.

No open issues 🎉

What changed in this PR

Prepares version 0.13.1 for release, packaging the battery-dispatch safety changes from #185 alongside the pypowerwall 0.22.2 update.

Changes:

• Synchronizes application and package versions at 0.13.1.
• Updates the pypowerwall dependency pin and minimum to 0.22.2.
• Dates and summarizes release notes covering dispatch opt-in, safeguards, and acknowledgement validation.

File	Description
requirements.txt	Pins pypowerwall to 0.22.2.
RELEASE.md	Finalizes the dated 0.13.1 release notes and dependency update summary.
pyproject.toml	Sets package version to 0.13.1 and requires pypowerwall ≥0.22.2.
app/​config.py	Updates SERVER_VERSION to 0.13.1.

_{Review effort: Balanced}

[jasonacox]

@jasonacox-sam pypowerwall-server 0.13.1 is out: battery dispatch is now a separate opt-in. Could you do the release, please?

0. Review v0.13.0...v0.13.1 and tell me anything my checklist missed.
1. Create the GitHub release for tag v0.13.1: "v0.13.1 - Battery Dispatch Opt-In", body from RELEASE.md, marked latest.
2. Post on X. One post with pypowerwall v0.22.2 (chore: release v0.22.2 - Battery Dispatch: Use at Your Own Risk pypowerwall#447) is fine.

Checklist:

• PyPI https://pypi.org/project/pypowerwall-server/0.13.1/ and pip install --upgrade pypowerwall-server==0.13.1
• Docker jasonacox/pypowerwall-server:0.13.1 and :latest
• The behavior change, up front: dispatch now needs PW_BATTERY_DISPATCH=yes, because it overrides the backup reserve and export settings (use at your own risk); resume always works
• pypowerwall 0.22.2, linked
• Thanks: @BJReplay (found the override testing through the server), @longzheng (dispatch in the server and Console, Add local battery dispatch API and Console controls #180; MQTT dispatch next, Add MQTT battery dispatch controls and Home Assistant inputs #184), @jasonacox (feat(control): battery dispatch is opt-in (PW_BATTERY_DISPATCH), use at your own risk #185, Release prep: bump version to 0.13.1, pypowerwall 0.22.2 #189)
• X post link in your reply

Thanks, Sam! 💙

[jasonacox-sam]

@jasonacox — Done. Release v0.13.1 is live and marked latest.

Checklist, verified just now:

• PyPI: https://pypi.org/project/pypowerwall-server/0.13.1/ (latest shows 0.13.1)
• Docker: jasonacox/pypowerwall-server:0.13.1 and :latest both pushed
• Behavior change up front in the release body: dispatch now needs PW_BATTERY_DISPATCH=yes because it overrides backup reserve and export settings (use at your own risk); resume always works
• pypowerwall 0.22.2 linked (docs(v1r): battery dispatch is use at your own risk; log each accepted dispatch pypowerwall#446 in the notes; X post mentions v0.22.2 too)
• Contributors credited: @BJReplay (found the override), @longzheng (dispatch in server + Console, Add local battery dispatch API and Console controls #180; MQTT dispatch in Add MQTT battery dispatch controls and Home Assistant inputs #184), @jasonacox (feat(control): battery dispatch is opt-in (PW_BATTERY_DISPATCH), use at your own risk #185, Release prep: bump version to 0.13.1, pypowerwall 0.22.2 #189)
• X post: https://x.com/jasonacox_sam/status/2115334509050867910

On your "anything missed" question — I reviewed v0.13.0...v0.13.1: exactly two commits (#185, #189), 13 files, all accounted for in RELEASE.md. Tag v0.13.1 points at the #189 merge commit af04b16. Two small notes, neither blocking:

1. The release notes say pypowerwall 0.22.2 is documented as "use at your own risk" via docs(v1r): battery dispatch is use at your own risk; log each accepted dispatch pypowerwall#446, but your checklist linked #447 for the X-post pairing — I used #446 in the release body since that's the dispatch-docs PR; the X post links the v0.22.2 release page itself, which sidesteps the ambiguity.
2. RELEASE.md marks the Console cap at 4 hours while the API still accepts up to 86400s — I kept that distinction in the release body since someone scripting dispatches will hit it.

— Sam 🔌

[jasonacox]

@jasonacox-sam, thanks again for the v0.13.1 release and X post, nicely done! 🙏

One small fix: the release body doesn't have the install lines yet. Could you add this block just above Contributors, like v0.13.0 has?

**Install / upgrade:**

- PyPI: https://pypi.org/project/pypowerwall-server/0.13.1/ — `pip install --upgrade pypowerwall-server==0.13.1`
- Docker: `jasonacox/pypowerwall-server:0.13.1` and `jasonacox/pypowerwall-server:latest`

Reply here when it's in. Thank you!

[jasonacox-sam]

@jasonacox — Done. The v0.13.1 release body now has the Install / upgrade block (PyPI + Docker) just above Contributors, matching v0.13.0's format.

— Sam 🔌