From 35db60125b8a85ff05ee3190d4fef3cbc926ba14 Mon Sep 17 00:00:00 2001 From: Ryan Malloy Date: Sun, 5 Jul 2026 09:14:29 -0600 Subject: [PATCH] Bump to 2026.7.5, use RFC 5737 IP in OTA docstring Version bump for release. Also sanitizes a 192.168.1.100 docstring example in ota_manager.py to 192.0.2.100 (RFC 5737 documentation range) so it can't be mistaken for a real target. --- pyproject.toml | 2 +- src/mcesptool/components/ota_manager.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/pyproject.toml b/pyproject.toml index 382fb1f..d5c15ea 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "hatchling.build" [project] name = "mcesptool" -version = "2026.02.25.1" +version = "2026.7.5" description = "FastMCP server for ESP32/ESP8266 development with esptool integration" readme = "README.md" requires-python = ">=3.10" diff --git a/src/mcesptool/components/ota_manager.py b/src/mcesptool/components/ota_manager.py index f0c712f..bbc586a 100644 --- a/src/mcesptool/components/ota_manager.py +++ b/src/mcesptool/components/ota_manager.py @@ -137,7 +137,7 @@ class OTAManager: """Deploy an OTA package to a device via HTTP POST. Extracts firmware.bin from the package and POSTs it to the - device's OTA endpoint (e.g. http://192.168.1.100/ota/update). + device's OTA endpoint (e.g. http://192.0.2.100/ota/update). The target device must be running an HTTP OTA server (like esp_https_ota or a custom handler). """