@alteriom/painlessmesh 1.8.14 → 1.9.0

package/docs/releases/FEATURE_HISTORY.md

@@ -1,543 +0,0 @@
-# Alteriom painlessMesh Feature History
-
-This document chronicles the major feature development phases that transformed
-painlessMesh into a production-ready, enterprise-grade mesh networking library.
-
-## Quick Navigation
-
-- [Phase 1 (v1.6.x)](#phase-1-ota-infrastructure--enhanced-monitoring) - OTA Infrastructure & Enhanced Monitoring
-- [Phase 2 (v1.7.x)](#phase-2-broadcast-ota--mqtt-bridge) - Broadcast OTA & MQTT Bridge
-- [Feature Comparison](#feature-comparison-matrix)
-- [Migration Guide](#migration-guide)
-- [Performance Metrics](#performance-metrics)
-
----
-
-## Phase 1: OTA Infrastructure & Enhanced Monitoring
-
-**Release:** v1.6.x | **Date:** December 2024 | **Status:** ✅ Complete
-
-### Overview
-
-Phase 1 established the foundation for efficient OTA updates and comprehensive
-device monitoring, focusing on infrastructure and backward compatibility.
-
-### Features Implemented
-
-#### 1. Compressed OTA Transfer
-
-**Description:** Infrastructure for bandwidth-efficient firmware distribution
-using compression flags.
-
-**Key Changes:**
-
-- Added `compressed` boolean flag to OTA message classes
-- Extended `offerOTA()` API to accept compression parameter
-- Full JSON serialization support for ArduinoJson 6 and 7
-- Foundation for 40-60% bandwidth reduction
-
-**Usage:**
-
-```cpp
-// Enable compressed OTA (40-60% bandwidth savings)
-mesh.offerOTA("sensor", "ESP32", md5, parts, false, false, true);
-//                                            ^^^^^ ^^^^^ ^^^^
-//                                            forced bcast compress
-```
-
-**Benefits:**
-
-- 40-60% bandwidth reduction (with compression library)
-- Faster firmware distribution
-- Lower energy consumption
-- Works with all distribution methods
-
-#### 2. Enhanced Status Package
-
-**Description:** Comprehensive device and mesh monitoring with 18 standardized
-fields for professional monitoring integration.
-
-**Key Changes:**
-
-- Created `EnhancedStatusPackage` class (Type ID 203)
-- 18 comprehensive fields:
-  - Device health (uptime, memory, WiFi, firmware)
-  - Mesh statistics (nodes, connections, messages)
-  - Performance metrics (latency, packet loss, throughput)
-  - Alert system (bit flags + error messages)
-
-**Usage:**
-
-```cpp
-alteriom::EnhancedStatusPackage status;
-status.uptime = millis() / 1000;
-status.freeMemory = ESP.getFreeHeap() / 1024;
-status.nodeCount = mesh.getNodeList().size();
-status.messagesReceived = getTotalRx();
-status.avgLatency = getAverageLatency();
-
-String msg;
-protocol::Variant(&status).printTo(msg);
-mesh.sendBroadcast(msg);
-```
-
-**Benefits:**
-
-- Comprehensive device and mesh monitoring
-- Proactive alert system
-- Standardized format across all Alteriom nodes
-- Ready for dashboard integration
-
-### Files Modified
-
-**Core Library (3 files):**
-
-- `src/painlessmesh/ota.hpp` - Compressed flag support
-- `src/painlessmesh/mesh.hpp` - Extended API
-- `examples/alteriom/alteriom_sensor_package.hpp` - EnhancedStatusPackage
-
-**Tests (1 file):**
-
-- `test/catch/catch_alteriom_packages.cpp` - 80 assertions, all passing
-
-**Documentation (3 files):**
-
-- `docs/PHASE1_GUIDE.md` - User guide
-- `docs/improvements/PHASE1_IMPLEMENTATION.md` - Technical details
-- `examples/alteriom/phase1_features.ino` - Working example
-
-### Performance Impact
-
-| Metric | Compressed OTA | Enhanced Status |
-|--------|----------------|-----------------|
-| Memory Overhead | +4-8KB (buffer) | +500 bytes |
-| Bandwidth Savings | 40-60% | N/A |
-| Update Time | 35-70s (vs 60-120s) | N/A |
-| Message Size | N/A | ~1.5KB |
-| CPU Overhead | Minimal | Negligible |
-| Recommended Interval | Per update | 30-60 seconds |
-
-### Success Criteria
-
-- ✅ Compressed OTA flag infrastructure in place
-- ✅ Enhanced status package with 18 comprehensive fields
-- ✅ Full backward compatibility maintained
-- ✅ Complete test coverage (80 assertions passing)
-- ✅ Comprehensive documentation written
-- ✅ Working examples provided
-- ✅ No breaking changes to existing APIs
-
----
-
-## Phase 2: Broadcast OTA & MQTT Bridge
-
-**Release:** v1.7.0 | **Date:** December 2024 | **Status:** ✅ Complete
-
-### Overview
-
-Phase 2 introduced true mesh-wide broadcast distribution and professional
-monitoring capabilities, enabling enterprise-grade deployments at scale.
-
-### Features Implemented
-
-#### 1. Broadcast OTA Distribution
-
-**Description:** Revolutionary firmware distribution where chunks are broadcast
-once to all nodes simultaneously, dramatically reducing network traffic.
-
-**Key Changes:**
-
-- Enhanced `Data::replyTo()` to set BROADCAST routing when `broadcasted=true`
-- Sender broadcasts each chunk once to all nodes
-- Automatic fallback to unicast for reliability
-- Parallel distribution to 50-100+ nodes
-
-**Usage:**
-
-```cpp
-// Enable broadcast mode (Phase 2 feature)
-mesh.offerOTA("sensor", "ESP32", md5, parts, false, true, true);
-//                                                    ^^^^ ^^^^
-//                                              broadcast compress
-```
-
-**Benefits:**
-
-- **98% network traffic reduction** for 50-node mesh
-- **Parallel distribution** - All nodes receive simultaneously
-- **O(F) time complexity** vs O(N×F) for unicast
-- **Memory efficient** - Only +2-5KB per node
-- **Scales to 50-100+ nodes** effectively
-
-**Performance:**
-
-| Mesh Size | Unicast Transmissions | Broadcast Transmissions | Reduction |
-|-----------|----------------------|------------------------|-----------|
-| 10 nodes  | 1,500 | 150 | 90% |
-| 50 nodes  | 7,500 | 150 | 98% |
-| 100 nodes | 15,000 | 150 | 99% |
-
-*Example: 150-chunk firmware update*
-
-#### 2. MQTT Status Bridge
-
-**Description:** Professional monitoring solution that publishes comprehensive
-mesh status to MQTT for integration with Grafana, InfluxDB, Prometheus, and
-other enterprise monitoring tools.
-
-**Key Changes:**
-
-- Created `MqttStatusBridge` class
-- Publishes to 5 MQTT topic streams:
-  - `mesh/status/nodes` - Node list with count
-  - `mesh/status/topology` - Complete mesh structure JSON
-  - `mesh/status/metrics` - Performance statistics
-  - `mesh/status/alerts` - Active alert conditions
-  - `mesh/status/node/{id}` - Per-node detailed status (optional)
-
-**Usage:**
-
-```cpp
-#include "examples/bridge/mqtt_status_bridge.hpp"
-
-MqttStatusBridge bridge(mesh, mqttClient);
-bridge.setPublishInterval(30000);  // 30 seconds
-bridge.enableTopology(true);
-bridge.enableMetrics(true);
-bridge.enableAlerts(true);
-bridge.begin();
-```
-
-**Benefits:**
-
-- **Professional monitoring tools** - Grafana, InfluxDB, Prometheus
-- **Cloud integration** via MQTT
-- **Real-time visibility** into mesh health
-- **Automated alerting** for critical conditions
-- **Configurable** - Enable/disable features, set intervals
-- **Scalable** - Efficient even with 50+ nodes
-
-**Integration Ready:**
-
-- Grafana dashboards for visualization
-- InfluxDB/Telegraf for time-series storage
-- Prometheus exporters for metrics
-- Home Assistant for automation
-- Node-RED for custom processing
-
-### Files Modified
-
-**Core Library (1 file):**
-
-- `src/painlessmesh/ota.hpp` - Broadcast OTA mode
-
-**New Components (2 files):**
-
-- `examples/bridge/mqtt_status_bridge.hpp` - Bridge implementation
-- `examples/bridge/mqtt_status_bridge_example.ino` - Complete example
-
-**Examples (1 file):**
-
-- `examples/alteriom/phase2_features.ino` - Phase 2 demo
-
-**Documentation (2 files):**
-
-- `docs/PHASE2_GUIDE.md` - User guide (~500 lines)
-- `docs/improvements/PHASE2_IMPLEMENTATION.md` - Technical details (~600 lines)
-
-### Performance Impact
-
-**Broadcast OTA:**
-
-| Metric | Small (10 nodes) | Medium (50 nodes) | Large (100 nodes) |
-|--------|------------------|-------------------|-------------------|
-| Traffic Reduction | 90% | 98% | 99% |
-| Update Time | ~10x faster | ~50x faster | ~100x faster |
-| Memory per Node | +2-5KB | +2-5KB | +2-5KB |
-
-**MQTT Status Bridge:**
-
-| Metric | Minimal Config | Standard Config | Full Config |
-|--------|----------------|-----------------|-------------|
-| Memory (root node) | +5-8KB | +5-8KB | +5-8KB |
-| MQTT Traffic/interval | ~500 bytes | ~2-3KB | ~10KB (50 nodes) |
-| Other nodes | 0 bytes | 0 bytes | 0 bytes |
-
-**Recommended Intervals:**
-
-- Small mesh (<10 nodes): 30 seconds
-- Medium mesh (10-50 nodes): 60 seconds
-- Large mesh (50+ nodes): 120 seconds
-
-### Success Criteria
-
-- ✅ Broadcast OTA scales to 50-100+ nodes
-- ✅ ~98% network traffic reduction demonstrated
-- ✅ MQTT Status Bridge production-ready
-- ✅ Professional monitoring tool integration enabled
-- ✅ Full backward compatibility maintained
-- ✅ Comprehensive documentation written
-- ✅ Working examples provided
-- ✅ No breaking changes
-
----
-
-## Feature Comparison Matrix
-
-### OTA Distribution Methods
-
-| Feature | Base | Phase 1 | Phase 2 |
-|---------|------|---------|---------|
-| Unicast OTA | ✅ | ✅ | ✅ |
-| Compressed Flag | ❌ | ✅ | ✅ |
-| Broadcast Distribution | ❌ | ❌ | ✅ |
-| Network Efficiency | Baseline | +40-60% | +90-99% |
-| Max Practical Nodes | 5-10 | 10-20 | 50-100+ |
-| Update Time Complexity | O(N×F) | O(N×F) | O(F) |
-
-### Monitoring & Status
-
-| Feature | Base | Phase 1 | Phase 2 |
-|---------|------|---------|---------|
-| Basic Status | ✅ | ✅ | ✅ |
-| Enhanced Status | ❌ | ✅ | ✅ |
-| MQTT Bridge | ❌ | ❌ | ✅ |
-| Grafana Integration | ❌ | ❌ | ✅ |
-| Alert System | ❌ | ✅ | ✅ |
-| Cloud Connectivity | ❌ | ❌ | ✅ |
-
-### Backward Compatibility
-
-| Base Code | Phase 1 | Phase 2 | Breaking Changes |
-|-----------|---------|---------|------------------|
-| ✅ Works | ✅ Works | ✅ Works | ❌ None |
-| Phase 1 Code | N/A | ✅ Works | ❌ None |
-| Phase 2 Code | ❌ | ❌ | N/A |
-
----
-
-## Migration Guide
-
-### From Base to Phase 1
-
-**No changes required** - All defaults preserve base behavior.
-
-**Optional: Enable Compression**
-
-```cpp
-// Before
-mesh.offerOTA(role, hardware, md5, parts);
-
-// After - add compression flag
-mesh.offerOTA(role, hardware, md5, parts, false, false, true);
-```
-
-**Optional: Use Enhanced Status**
-
-```cpp
-// Before
-alteriom::StatusPackage status;
-status.uptime = millis() / 1000;
-
-// After - use enhanced package
-alteriom::EnhancedStatusPackage status;
-status.uptime = millis() / 1000;
-status.nodeCount = mesh.getNodeList().size(); // New field
-```
-
-### From Phase 1 to Phase 2
-
-**No changes required** - All Phase 1 code continues to work.
-
-**Optional: Enable Broadcast OTA**
-
-```cpp
-// Phase 1
-mesh.offerOTA(role, hardware, md5, parts, false, false, true);
-
-// Phase 2 - add broadcast flag
-mesh.offerOTA(role, hardware, md5, parts, false, true, true);
-//                                                    ^^^^
-```
-
-**Optional: Add MQTT Bridge**
-
-```cpp
-#include "examples/bridge/mqtt_status_bridge.hpp"
-
-MqttStatusBridge bridge(mesh, mqttClient);
-bridge.setPublishInterval(30000);
-bridge.begin();
-```
-
-### Combined Usage (All Features)
-
-```cpp
-// Use all features together for maximum efficiency
-
-// Phase 1 + Phase 2: Broadcast + Compressed OTA
-mesh.offerOTA(role, hw, md5, parts, false, true, true);
-
-// Phase 1: Enhanced Status Package
-alteriom::EnhancedStatusPackage status;
-status.uptime = millis() / 1000;
-status.nodeCount = mesh.getNodeList().size();
-mesh.sendBroadcast(status.toJsonString());
-
-// Phase 2: MQTT Status Bridge
-MqttStatusBridge bridge(mesh, mqttClient);
-bridge.begin();
-```
-
----
-
-## Performance Metrics
-
-### Network Traffic Comparison
-
-**Scenario:** 150-chunk firmware update to N nodes
-
-| Nodes | Base (Unicast) | Phase 1 (Compressed) | Phase 2 (Broadcast) |
-|-------|----------------|----------------------|---------------------|
-| 5     | 750 tx         | 450 tx (-40%)        | 150 tx (-80%)       |
-| 10    | 1,500 tx       | 900 tx (-40%)        | 150 tx (-90%)       |
-| 20    | 3,000 tx       | 1,800 tx (-40%)      | 150 tx (-95%)       |
-| 50    | 7,500 tx       | 4,500 tx (-40%)      | 150 tx (-98%)       |
-| 100   | 15,000 tx      | 9,000 tx (-40%)      | 150 tx (-99%)       |
-
-### Update Time Comparison
-
-**Scenario:** 150 chunks × 100ms transmission time = 15 seconds per node (unicast)
-
-| Nodes | Base (Sequential) | Phase 2 (Parallel) | Speedup |
-|-------|-------------------|-------------------|---------|
-| 5     | 75 seconds        | 15 seconds        | 5x      |
-| 10    | 150 seconds       | 15 seconds        | 10x     |
-| 20    | 300 seconds       | 15 seconds        | 20x     |
-| 50    | 750 seconds       | 15 seconds        | 50x     |
-| 100   | 1,500 seconds     | 15 seconds        | 100x    |
-
-### Memory Usage
-
-| Feature | ESP8266 | ESP32 | Notes |
-|---------|---------|-------|-------|
-| Base | ~40KB | ~50KB | Baseline |
-| Phase 1 Compression | +4-8KB | +4-8KB | Decompression buffer |
-| Phase 1 Enhanced Status | +500 bytes | +500 bytes | Per status report |
-| Phase 2 Broadcast | +2-5KB | +2-5KB | Chunk tracking |
-| Phase 2 MQTT Bridge | N/A | +5-8KB | Root node only |
-
----
-
-## Recommended Usage
-
-### When to Use Each Phase
-
-**Phase 1 (Compressed OTA + Enhanced Status):**
-
-✅ Recommended for:
-
-- Any production deployment
-- Memory-constrained devices (ESP8266)
-- Bandwidth optimization without complexity
-- Comprehensive device monitoring
-
-**Phase 2 (Broadcast OTA + MQTT Bridge):**
-
-✅ Recommended for:
-
-- Meshes with 10+ nodes
-- All nodes need same firmware
-- Fast distribution is critical
-- Enterprise monitoring requirements
-- Cloud integration needs
-- Large-scale deployments (50-100+ nodes)
-
-❌ Not recommended for:
-
-- Very small meshes (<5 nodes) - overhead not justified
-- Heterogeneous firmware - different firmware per node
-- Pure offline systems - MQTT requires external network
-
----
-
-## Known Limitations
-
-### Phase 1
-
-1. **Compression library not integrated** - `compressed` flag is infrastructure only
-2. **Manual metrics collection** - EnhancedStatusPackage fields must be manually populated
-3. **Basic alert system** - Alert flag meanings are conventional, not enforced
-
-### Phase 2
-
-1. **Broadcast no per-node targeting** - All nodes receive all chunks
-   - Workaround: Use role/hardware filtering
-2. **Network reliability** - Broadcast packets may be dropped
-   - Mitigation: Automatic fallback to unicast
-3. **MQTT single point of failure** - Bridge node must remain online
-   - Mitigation: Use reliable hardware for bridge
-
----
-
-## Future Phases
-
-### Phase 3 (Planned)
-
-According to FEATURE_PROPOSALS.md:
-
-- Progressive Rollout OTA - Phased deployment with health checks
-- Real-time Telemetry Streams - Continuous metrics streaming
-- Proactive Alerting System - Automated anomaly detection
-- Large-scale Mesh Support - 100+ nodes optimization
-
-### Long-term Enhancements
-
-- Chunk bitmap tracking for better reliability
-- Adaptive rate limiting based on mesh congestion
-- MQTT command/control interface
-- Remote OTA triggering via MQTT
-- Integration with cloud platforms (AWS IoT, Azure IoT)
-
----
-
-## Documentation References
-
-### User Guides
-
-- [PHASE1_GUIDE.md](PHASE1_GUIDE.md) - Phase 1 complete user guide
-- [PHASE2_GUIDE.md](PHASE2_GUIDE.md) - Phase 2 complete user guide
-- [RELEASE_NOTES_1.7.0.md](RELEASE_NOTES_1.7.0.md) - v1.7.0 detailed release notes
-
-### Implementation Details
-
-- [PHASE1_IMPLEMENTATION.md](../improvements/PHASE1_IMPLEMENTATION.md) - Phase 1 technical details
-- [PHASE2_IMPLEMENTATION.md](../improvements/PHASE2_IMPLEMENTATION.md) - Phase 2 technical details
-- [FEATURE_PROPOSALS.md](../improvements/FEATURE_PROPOSALS.md) - Original proposals
-
-### Examples
-
-- [examples/alteriom/phase1_features.ino](../../examples/alteriom/phase1_features.ino) - Phase 1 demo
-- [examples/alteriom/phase2_features.ino](../../examples/alteriom/phase2_features.ino) - Phase 2 demo
-- [examples/bridge/mqtt_status_bridge_example.ino](../../examples/bridge/mqtt_status_bridge_example.ino) - MQTT bridge
-
----
-
-## Questions & Support
-
-1. **Documentation:** Start with the phase-specific guides above
-2. **Examples:** Check the working examples in the repository
-3. **Issues:** Search [GitHub Issues](https://github.com/Alteriom/painlessMesh/issues)
-4. **Discussions:** Post in [GitHub Discussions](https://github.com/Alteriom/painlessMesh/discussions)
-5. **Bug Reports:** Include logs, configuration, and mesh size
-
----
-
-**Summary:**
-
-- **Phase 1 (v1.6.x):** Foundation - Compressed OTA + Enhanced Monitoring
-- **Phase 2 (v1.7.0):** Scale - Broadcast OTA + MQTT Bridge
-- **Result:** Production-ready library scaling to 50-100+ nodes
-- **All phases:** Fully backward compatible, no breaking changes
-
-**Total Value:** 98% traffic reduction + enterprise monitoring + cloud integration

package/docs/releases/GITHUB_RELEASE_v1.8.6.md

@@ -1,71 +0,0 @@
-## 🐛 Bug Fixes
-
-### Bridge Failover Auto-Election (Issue #117)
-
-Fixed critical issue where mesh networks would remain bridgeless indefinitely when all nodes started without a designated initial bridge.
-
-**Before:** No initial bridge → no election → mesh stays bridgeless forever  
-**After:** No initial bridge → 60s startup → monitoring detects absence → election triggered → best RSSI node becomes bridge
-
-#### Implementation Details
-- Added periodic monitoring task (30s interval) that detects absence of healthy bridge
-- Activates after 60s startup grace period to allow network stabilization
-- Randomized election delay (1-3s) prevents thundering herd problem
-- Respects existing safeguards: election state, 60s cooldown, router visibility
-
-Fully backward compatible - pre-designated bridge mode continues to work as before.
-
-**Core fix:** `src/arduino/wifi.hpp`
-
-## 📝 Documentation
-
-### Bridge Failover Example
-
-Enhanced documentation to clarify two deployment modes:
-
-- **Auto-Election Mode**: All nodes regular (`INITIAL_BRIDGE=false`), RSSI-based election after 60s
-- **Pre-Designated Mode**: Traditional single initial bridge setup
-
-Updated:
-- `examples/bridge_failover/bridge_failover.ino` - Enhanced header comments
-- `examples/bridge_failover/README.md` - Comprehensive auto-election documentation
-
-## 🔧 Housekeeping
-
-- Synchronized `package-lock.json` version to 1.8.5
-
-## 📦 Installation
-
-### PlatformIO
-```ini
-lib_deps = alteriom/AlteriomPainlessMesh@^1.8.6
-```
-
-### NPM
-```bash
-npm install @alteriom/painlessmesh@1.8.6
-```
-
-### Arduino Library Manager
-Search for "AlteriomPainlessMesh" and update through the IDE
-
-## 🎯 Use Cases
-
-This release is valuable for:
-- Dynamic mesh networks with changing node positions
-- Fault-tolerant deployments requiring automatic bridge recovery
-- IoT systems with minimal human oversight
-- Development environments without pre-configured bridges
-
-## 🙏 Credits
-
-Special thanks to @woodlist for reporting the issue and providing detailed logs.
-
-## 📚 Resources
-
-- [Full Release Notes](https://github.com/Alteriom/painlessMesh/blob/main/docs/releases/RELEASE_NOTES_v1.8.6.md)
-- [Bridge Failover Example](https://github.com/Alteriom/painlessMesh/tree/main/examples/bridge_failover)
-- [Issue #117](https://github.com/Alteriom/painlessMesh/issues/117)
-- [Pull Request #118](https://github.com/Alteriom/painlessMesh/pull/118)
-
-**Full Changelog**: https://github.com/Alteriom/painlessMesh/compare/v1.8.5...v1.8.6

package/docs/releases/GITHUB_RELEASE_v1.8.7.md

@@ -1,90 +0,0 @@
-# AlteriomPainlessMesh v1.8.7
-
-**Release Date:** November 12, 2025  
-**Type:** Patch Release - Bug Fixes & Documentation
-
-## 🐛 Bug Fixes
-
-### Bridge Internet Connectivity Detection
-
-Fixed incorrect internet status reporting in bridge nodes:
-- **Before:** Bridge → Router (with Internet) → Reports "Internet: NO" ❌
-- **After:** Bridge → Router (with Internet) → Reports "Internet: YES" ✅
-
-Bridge nodes now properly check for actual internet connectivity by verifying both WiFi connection status AND valid gateway IP (not 0.0.0.0).
-
-**Impact:**
-- ✅ Accurate internet status for bridge nodes
-- ✅ Correct bridge failover behavior
-- ✅ No more false positives on regular nodes
-
-**Files changed:** `src/arduino/wifi.hpp`
-
-### Version Documentation Consistency
-
-Fixed confusing version numbers in header files:
-- Updated `painlessMesh.h` version comment: 1.8.4 → 1.8.7
-- Updated `AlteriomPainlessMesh.h` version defines: 1.6.1 → 1.8.7
-- Created comprehensive VERSION_MANAGEMENT.md documentation
-
-**Clarification:** Header file version comments indicate the library version when documentation was reviewed, not file-specific versioning. Use `library.properties` for the official version.
-
-## 📚 New Documentation
-
-### VERSION_MANAGEMENT.md
-
-New comprehensive guide explaining:
-- ✅ What version numbers in header files mean
-- ✅ Where to find the official library version
-- ✅ How to track file modification history
-- ✅ Version update workflow and best practices
-
-**Essential reading for contributors!**
-
-## 📦 Installation
-
-### Arduino Library Manager
-```
-Sketch → Include Library → Manage Libraries → 
-Search "AlteriomPainlessMesh" → Update to 1.8.7
-```
-
-### PlatformIO
-```ini
-lib_deps = alteriom/AlteriomPainlessMesh@^1.8.7
-```
-
-### NPM
-```bash
-npm install @alteriom/painlessmesh@1.8.7
-```
-
-## 🔄 Upgrade Notes
-
-**Fully backward compatible** with v1.8.6. No breaking changes.
-
-## 📖 Documentation
-
-- **Release Notes:** [docs/releases/RELEASE_NOTES_v1.8.7.md](docs/releases/RELEASE_NOTES_v1.8.7.md)
-- **Version Management Guide:** [docs/VERSION_MANAGEMENT.md](docs/VERSION_MANAGEMENT.md)
-- **Full Changelog:** [CHANGELOG.md](CHANGELOG.md)
-- **Online Documentation:** https://alteriom.github.io/painlessMesh/
-
-## 🔗 Links
-
-- **NPM Package:** https://www.npmjs.com/package/@alteriom/painlessmesh
-- **PlatformIO Registry:** https://registry.platformio.org/libraries/alteriom/AlteriomPainlessMesh
-- **Report Issues:** https://github.com/Alteriom/painlessMesh/issues
-
-## ✅ Checksums
-
-**Library Package:** `painlessMesh-v1.8.7.zip`
-- Will be generated automatically by GitHub Actions
-
-## 🙏 Credits
-
-Thanks to our users for reporting issues and helping improve the library!
-
----
-
-**Full Changelog:** https://github.com/Alteriom/painlessMesh/compare/v1.8.6...v1.8.7