@alteriom/painlessmesh 2.0.0 → 2.0.1

package/CHANGELOG.md

@@ -7,6 +7,60 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.0.1] - 2026-09-07
+
+A packaging and documentation release. **No library behaviour changed**: the
+mesh, routing, gateway, failover and OTA code of 2.0.1 is 2.0.0's, and the only
+edit under `src/` is the version macro. It exists to repair two defects in what
+2.0.0 *shipped*, both of which cost a user time before they ever compile
+anything.
+
+### Fixed
+
+- **The installation instructions shipped in 2.0.0 name a PlatformIO package
+  that has no 2.0.0.** The README, user guide and documentation site gave
+  `alteriom/AlteriomPainlessMesh`, and that registry owner stops at 1.10.0 — its
+  account is not one this project can publish from. Every automated release
+  since 1.7.6 went out under `sparck75`, which is now what the documentation
+  names. **Name the owner in `lib_deps`**: the bare name `AlteriomPainlessMesh`
+  matches both owners and PlatformIO warns rather than choosing.
+
+  ```ini
+  lib_deps =
+      sparck75/AlteriomPainlessMesh@^2.0.0
+  ```
+
+- **The v2.0.0 GitHub release carries no library archive.** This repository
+  publishes immutable releases, so the workflow's upload step — which ran after
+  the release was created — was refused with HTTP 422. The job failed before its
+  release decision, which also skipped the npm, GitHub Packages and PlatformIO
+  jobs; those three were published by hand. The archive is now attached in the
+  same call that creates the release, and the decision to publish is taken
+  before any step that can fail, so a failed upload can no longer suppress the
+  publications.
+
+- **PlatformIO publication went under the token's account rather than the
+  organisation.** `pio pkg publish` files a package under the account unless
+  `--owner` names the owner, and the workflow never passed it — which is how the
+  duplicate ownership above arose in the first place. It now passes `--owner`,
+  checks the version against that owner's own version table (the previous check
+  read a `Version:` line `pio pkg show` never prints), publishes the release
+  tag's sources rather than whichever branch was dispatched, and treats an
+  already-listed version as success instead of a failure.
+
+- **`scripts/validate-release.sh` reported a version mismatch that was not
+  there.** Without `jq` it fell back to a grep that matches every `"version"`
+  line in `library.json`, dependencies included, so the value it compared was
+  multi-line. It takes the first match now — the top-level one. CI was never
+  affected; it has `jq`.
+
+### Upgrading
+
+Nothing in the library behaves differently, so upgrading from 2.0.0 is optional.
+Take it if you install through PlatformIO, or if you want the release archive
+attached to the GitHub release. Everything in the 2.0.0 entry below still
+applies, including its *Before you upgrade* section.
+
 ## [2.0.0] - 2026-09-07
 
 painlessMesh 2.0 is a major release. It adds per-message delivery
@@ -317,6 +371,11 @@ processes scan results from the loop for that reason (see the ESP32 entry).
   every PR like the other twenty.
 - `keywords.txt` now lists the bridge, gateway, failover, queue and capacity
   API so the Arduino IDE highlights it.
+- **PlatformIO package owner.** 2.0.0 is published as `sparck75/AlteriomPainlessMesh`,
+  the owner every automated release since 1.7.6 went under. The registry also
+  holds `alteriom/AlteriomPainlessMesh`, which stops at 1.10.0: its account is
+  not one the project can publish from. Name the owner in `lib_deps`; the bare
+  name matches both.
 
 ### Added (post-review series)
 

package/README.md

@@ -11,7 +11,7 @@
 [![Release](https://github.com/Alteriom/painlessMesh/actions/workflows/release.yml/badge.svg)](https://github.com/Alteriom/painlessMesh/actions/workflows/release.yml)
 [![GitHub release](https://img.shields.io/github/v/release/Alteriom/painlessMesh?label=version)](https://github.com/Alteriom/painlessMesh/releases)
 [![NPM Version](https://img.shields.io/npm/v/@alteriom/painlessmesh?label=npm)](https://www.npmjs.com/package/@alteriom/painlessmesh)
-[![PlatformIO Registry](https://badges.registry.platformio.org/packages/alteriom/library/AlteriomPainlessMesh.svg)](https://registry.platformio.org/libraries/alteriom/AlteriomPainlessMesh)
+[![PlatformIO Registry](https://badges.registry.platformio.org/packages/sparck75/library/AlteriomPainlessMesh.svg)](https://registry.platformio.org/libraries/sparck75/AlteriomPainlessMesh)
 
 </div>
 
@@ -410,11 +410,11 @@ git clone https://github.com/Alteriom/painlessMesh.git AlteriomPainlessMesh
 
 ### PlatformIO
 
-The library is published on the [PlatformIO registry](https://registry.platformio.org/libraries/alteriom/AlteriomPainlessMesh) as `alteriom/AlteriomPainlessMesh`:
+The library is published on the [PlatformIO registry](https://registry.platformio.org/libraries/sparck75/AlteriomPainlessMesh) as `sparck75/AlteriomPainlessMesh`. The registry also lists an `alteriom/AlteriomPainlessMesh` that stops at 1.10.0; its owner account is not one the project can publish from, so 2.0.0 and later live under `sparck75`, which has carried every automated release since 1.7.6. Name the owner in `lib_deps`, since the bare name matches both:
 
 ```ini
 lib_deps =
-    alteriom/AlteriomPainlessMesh@^2.0.0
+    sparck75/AlteriomPainlessMesh@^2.0.0
 ```
 
 ### Dependencies
@@ -596,9 +596,11 @@ These are the message types used by applications built on painlessMesh:
 - **Event Coordination** - Synchronized displays, distributed processing
 - **Bridge Networks** - Connect mesh to WiFi/Internet/MQTT - [📖 Bridge Guide](BRIDGE_TO_INTERNET.md)
 
-## Latest Release: v2.0.0 (September 7, 2026)
+## Latest Release: v2.0.1 (September 7, 2026)
 
-**Delivery confirmation, a unified send path, and a mesh that holds together on real hardware**
+**A packaging fix over 2.0.0 — no library behaviour changed.** 2.0.0's installation instructions named a PlatformIO package that has no 2.0.0 (`alteriom/…` stops at 1.10.0; releases go out under `sparck75`), and its GitHub release carries no library archive because the upload was refused by an immutable release. Both are fixed; upgrading from 2.0.0 is optional.
+
+**2.0.0 — delivery confirmation, a unified send path, and a mesh that holds together on real hardware**
 
 - `sendSingle()` and `sendBroadcast()` accept a delivery callback — it fires with `delivered=true` and the round-trip latency on acknowledgment, or `delivered=false` on timeout — and a `SendOptions` struct that carries a priority and a callback in one call. Priority is kept across hops.
 - Thirty-odd defects in gateway failover, channel following, routing and the station scan, every one found in the serial logs of a six-family hardware rig and fixed there: a bridge that stops says so, the mesh follows an elected bridge to its channel and treats it as home, a node is in one place in every neighbour's tree, a dead connection is not a route, a stale scan does not consume a live one.

package/RELEASE_GUIDE.md

@@ -21,7 +21,12 @@ the version commit reaches `main`.
    workflow owns tags and publication.
 
    The workflow tags only when the push to `main` carries a version-file
-   change or a head commit whose message starts with `release:`. When the
+   change or a head commit whose message starts with `release:`. The
+   repository publishes immutable releases: a release takes its assets and
+   notes when it is created and cannot be edited afterwards, so a failed
+   publication is repaired by `manual-publish.yml` (npm, GitHub Packages) and
+   `platformio-publish.yml`, both dispatched with the tag, not by re-running
+   the release workflow. When the
    version metadata was bumped earlier in the cycle (as for 2.0.0), merge the
    release pull request with a commit titled `release: vX.Y.Z` — a squash or
    merge commit with that title — or the push is ignored.

package/examples/sendToInternet/platformio.ini

@@ -9,7 +9,7 @@ platform = espressif32
 board = esp32dev
 framework = arduino
 lib_deps = 
-    alteriom/AlteriomPainlessMesh
+    sparck75/AlteriomPainlessMesh
     bblanchon/ArduinoJson@^7.0.0
 monitor_speed = 115200
 
@@ -18,6 +18,6 @@ platform = espressif8266
 board = nodemcuv2
 framework = arduino
 lib_deps = 
-    alteriom/AlteriomPainlessMesh
+    sparck75/AlteriomPainlessMesh
     bblanchon/ArduinoJson@^7.0.0
 monitor_speed = 115200

package/library.json

@@ -6,7 +6,7 @@
     "type": "git",
     "url": "https://github.com/Alteriom/painlessMesh"
   },
-  "version": "2.0.0",
+  "version": "2.0.1",
   "frameworks": [
     "arduino"
   ],

package/library.properties

@@ -1,5 +1,5 @@
 name=Alteriom PainlessMesh
-version=2.0.0
+version=2.0.1
 author=Coopdis,Scotty Franzyshen,Edwin van Leeuwen,Germán Martín,Maximilian Schwarz,Doanh Doanh,Alteriom
 maintainer=Alteriom
 sentence=A painless way to setup a mesh with ESP8266 and ESP32 devices with Alteriom extensions

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alteriom/painlessmesh",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "description": "painlessMesh is a user-friendly library for creating mesh networks with ESP8266 and ESP32 devices. This Alteriom fork includes additional packages for sensor data (SensorPackage), device commands (CommandPackage), and status monitoring (StatusPackage). It handles routing and network management automatically, so you can focus on your application. The library uses JSON-based messaging and syncs time across all nodes, making it ideal for coordinated behaviour like synchronized light displays or sensor networks reporting to a central node.",
   "keywords": [
     "arduino",

package/src/AlteriomPainlessMesh.h

@@ -29,10 +29,10 @@
 /**
  * @brief AlteriomPainlessMesh library version information
  */
-#define ALTERIOM_PAINLESS_MESH_VERSION "2.0.0"
+#define ALTERIOM_PAINLESS_MESH_VERSION "2.0.1"
 #define ALTERIOM_PAINLESS_MESH_VERSION_MAJOR 2
 #define ALTERIOM_PAINLESS_MESH_VERSION_MINOR 0
-#define ALTERIOM_PAINLESS_MESH_VERSION_PATCH 0
+#define ALTERIOM_PAINLESS_MESH_VERSION_PATCH 1
 
 /**
  * @brief Library description and usage information