Skip to content

nlbwmon: enhance init script with logging and health checks - #29709

Open
Mahmudul-009 wants to merge 3 commits into
openwrt:masterfrom
Mahmudul-009:patch-3
Open

nlbwmon: enhance init script with logging and health checks#29709
Mahmudul-009 wants to merge 3 commits into
openwrt:masterfrom
Mahmudul-009:patch-3

Merge branch 'master' into patch-3

e218ea5
Select commit
Loading
Failed to load commit list.
OpenWrt / FormalityCheck / OpenWrt Makefiles failed Aug 13, 2026 in 0s

OpenWrt Makefiles: Failed

Some package files need fixing — open the details below to see what to change.

Details

Checking PR #29709: nlbwmon: enhance init script with logging and health checks (Makefile Audit)

Commit 5332e70 - Enhance nlbwmon with logging, health checks, and options:

✅ File additions contain clean UNIX (LF) line termination
✅ All modified files contain a trailing newline

Commit 85e2d43 - Refactor logging functions and improve error handling:

✅ File additions contain clean UNIX (LF) line termination
✅ All modified files contain a trailing newline

Commit e218ea5 - Merge branch 'master' into patch-3:

✅ Mandatory structural metadata present: 'PKG_MAINTAINER'
✅ Mandatory structural metadata present: 'PKG_LICENSE'
✅ Mandatory structural metadata present: 'PKG_LICENSE_FILES'
✅ PKG_MAINTAINER email address format is valid: 'tiagogaspar8@gmail.com'
✅ PKG_MAINTAINER email address format is valid: 'mstam@ripe.net'
✅ PKG_MAINTAINER email address format is valid: 'stangri@melmac.ca'
✅ PKG_MAINTAINER email address format is valid: 'egc112@msn.com'
✅ PKG_MAINTAINER email address format is valid: 'flokli@flokli.de'
✅ PKG_MAINTAINER email address format is valid: 'michel.promonet@free.fr'
✅ PKG_MAINTAINER email address format is valid: 'pepe.schlehofer@gmail.com'
✅ PKG_MAINTAINER email address format is valid: 'toke@toke.dk'
✅ PKG_MAINTAINER email address format is valid: 'toke@toke.dk'
✅ PKG_MAINTAINER email address format is valid: 'vincent@systemli.org'
✅ New init scripts declare the rc.common interpreter and a START= priority
✅ Makefile conffiles macro properly registers INSTALL_CONF tracking parameters
✅ Makefile conffiles macro properly registers INSTALL_CONF tracking parameters
✅ Makefile conffiles macro properly registers INSTALL_CONF tracking parameters
✅ Makefile conffiles macro properly registers INSTALL_CONF tracking parameters
✅ Makefile conffiles macro properly registers INSTALL_CONF tracking parameters
✅ Makefile conffiles macro properly registers INSTALL_CONF tracking parameters
✅ Makefile conffiles macro properly registers INSTALL_CONF tracking parameters
✅ Makefile conffiles block contains no spaces or indentation and paths are correctly formatted
✅ Makefile does not assign per-package variables at the top level
✅ Makefile contains valid assignment operators and no spaces after ':='
✅ Makefile blocks contain valid indentation (spaces for metadata/description, tabs for build/install recipes)
✅ No feed package forces its own inclusion into buildbot default images via DEFAULT+BUILDBOT
✅ Makefile does not reuse PKG_NAME in call, define, or eval lines
✅ File additions contain clean UNIX (LF) line termination
✅ All modified files contain a trailing newline
✅ Configuration file 'net/nut/files/nut_server' destined for '/etc/config/' is a valid UCI configuration file
✅ Configuration file 'net/nut/files/nut_server' destined for '/etc/config/' is a valid UCI configuration file
✅ Configuration file 'net/nut/files/nut_monitor' destined for '/etc/config/' is a valid UCI configuration file
✅ Configuration file 'net/nut/files/nut_server' destined for '/etc/config/' is a valid UCI configuration file
✅ Configuration file 'net/nut/files/nut_monitor' destined for '/etc/config/' is a valid UCI configuration file
✅ Configuration file 'net/nut/files/nut_server' destined for '/etc/config/' is a valid UCI configuration file
✅ Configuration file 'net/privoxy/files/privoxy.config' destined for '/etc/config/' is a valid UCI configuration file
✅ Configuration file 'net/ripe-atlas/files/ripe-atlas.conf' destined for '/etc/config/' is a valid UCI configuration file
✅ Configuration file 'net/https-dns-proxy/files/etc/config/https-dns-proxy' destined for '/etc/config/' is a valid UCI configuration file
✅ Configuration file 'net/trafficshaper/files/trafficshaper.conf' destined for '/etc/config/' is a valid UCI configuration file
✅ Configuration file 'admin/zabbix/files/zabbix_agentd.config' destined for '/etc/config/' is a valid UCI configuration file
✅ Configuration file 'admin/zabbix/files/zabbix_server.config' destined for '/etc/config/' is a valid UCI configuration file
✅ Configuration file 'admin/zabbix/files/zabbix_proxy.config' destined for '/etc/config/' is a valid UCI configuration file
✅ Configuration file 'net/hev-socks5-tunnel/files/hev-socks5-tunnel.config' destined for '/etc/config/' is a valid UCI configuration file
⚠️ Warning: PKG_LICENSE value 'NPSL-0.95' is not a known SPDX identifier. Pick the matching identifier from https://spdx.org/licenses/, or write it as LicenseRef-<name> if this license is not on the SPDX list.
❌ Makefile introduces PKG_VERSION '1.14.6', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.14.6'.
❌ Makefile introduces PKG_VERSION '2.1.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.1.2'.
❌ Makefile introduces PKG_VERSION '2026.7.4', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2026.7.4'.
❌ Makefile introduces PKG_VERSION '0.107.78', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.107.78'.
❌ Makefile introduces PKG_VERSION '2026.27', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2026.27'.
❌ Makefile introduces PKG_VERSION '7.1.0.2026070800', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 7.1.0.2026070800'.
❌ Makefile introduces PKG_VERSION '3.53.3', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.53.3'.
❌ Makefile introduces PKG_VERSION '1.3.6', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.3.6'.
❌ Makefile introduces PKG_VERSION '2.2.5', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.2.5'.
❌ Makefile introduces PKG_VERSION '29.6.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 29.6.1'.
❌ Makefile introduces PKG_VERSION '29.6.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 29.6.1'.
❌ Makefile introduces PKG_VERSION '7.0.28', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 7.0.28'.
❌ Makefile introduces PKG_VERSION '8.2606.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 8.2606.0'.
❌ Makefile introduces PKG_VERSION '2026.05.06', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2026.05.06'.
❌ Makefile introduces PKG_VERSION '0.14.12', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.14.12'.
❌ Makefile introduces PKG_VERSION '1.39.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.39.2'.
❌ Makefile introduces PKG_VERSION '3.7.7', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.7.7'.
❌ Makefile introduces PKG_VERSION '9.07.2907', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 9.07.2907'.
❌ Makefile introduces PKG_VERSION '4.18.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 4.18.0'.
❌ Makefile introduces PKG_VERSION '1.9.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.9.2'.
❌ Makefile introduces PKG_VERSION '3.5.6', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.5.6'.
❌ Makefile introduces PKG_VERSION '2.16.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.16.0'.
❌ Makefile introduces PKG_VERSION '3.2.10', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.2.10'.
❌ Makefile introduces PKG_VERSION '9.20.26', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 9.20.26'.
❌ Makefile introduces PKG_VERSION '1.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.1'.
❌ Makefile introduces PKG_VERSION '5.51.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 5.51.2'.
❌ Makefile introduces PKG_VERSION '2026.7.3', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2026.7.3'.
❌ Makefile introduces PKG_VERSION '8.0.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 8.0.0'.
❌ Makefile introduces PKG_VERSION '3.4.9', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.4.9'.
❌ Makefile introduces PKG_VERSION '3.18', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.18'.
❌ Makefile introduces PKG_VERSION '2026.7.22', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2026.7.22'.
❌ Makefile introduces PKG_VERSION '4.1.4', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 4.1.4'.
❌ Makefile introduces PKG_VERSION '1.9.8', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.9.8'.
❌ Makefile introduces PKG_VERSION '1.18.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.18.0'.
❌ Makefile introduces PKG_VERSION '1.25.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.25.0'.
❌ Makefile introduces PKG_VERSION '2.15.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.15.1'.
❌ Makefile introduces PKG_VERSION '3.53.4', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.53.4'.
❌ Makefile introduces PKG_VERSION '2.3.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.3.1'.
❌ Makefile introduces PKG_VERSION '2.12.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.12.0'.
❌ Makefile introduces PKG_VERSION '1.0.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.0.0'.
❌ Makefile introduces PKG_VERSION '1.2.5', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.2.5'.
❌ Makefile introduces PKG_VERSION '0.3.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.3.2'.
❌ Makefile introduces PKG_VERSION '0.12.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.12.1'.
❌ Makefile introduces PKG_VERSION '1.11.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.11.0'.
❌ Makefile introduces PKG_VERSION '2.15.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.15.2'.
❌ Makefile introduces PKG_VERSION '2.15.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.15.1'.
❌ Makefile introduces PKG_VERSION '1.25.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.25.2'.
❌ Makefile introduces PKG_VERSION '0.3.34', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.3.34'.
❌ Makefile introduces PKG_VERSION '3.2.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.2.0'.
❌ Makefile introduces PKG_VERSION '0.409', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.409'.
❌ Makefile introduces PKG_VERSION '13.0.6', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 13.0.6'.
❌ Makefile introduces PKG_VERSION '4.1.3', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 4.1.3'.
❌ Makefile introduces PKG_VERSION '1.8.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.8.2'.
❌ Makefile introduces PKG_VERSION '704', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 704'.
❌ Makefile introduces PKG_VERSION '1.2.16.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.2.16.1'.
❌ Makefile introduces PKG_VERSION '2.1.18', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.1.18'.
❌ Makefile introduces PKG_VERSION '7.7', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 7.7'.
❌ Makefile introduces PKG_VERSION '28', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 28'.
❌ Makefile introduces PKG_VERSION '0.3.29', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.3.29'.
❌ Makefile introduces PKG_VERSION '2.1.7', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.1.7'.
❌ Makefile introduces PKG_VERSION '1.70.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.70.0'.
❌ Makefile introduces PKG_VERSION '22.23.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 22.23.2'.
❌ Makefile introduces PKG_VERSION '4.5.7', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 4.5.7'.
❌ Makefile introduces PKG_VERSION '9.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 9.2'.
❌ Makefile introduces PKG_VERSION '2.8.7', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.8.7'.
❌ Makefile introduces PKG_VERSION '2.4.7', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.4.7'.
❌ Makefile introduces PKG_VERSION '1.8.11', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.8.11'.
❌ Makefile introduces PKG_VERSION '2026.08.06', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2026.08.06'.
❌ Makefile introduces PKG_VERSION '7.1.2.29', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 7.1.2.29'.
❌ Makefile introduces PKG_VERSION '1.3.48', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.3.48'.
❌ Makefile introduces PKG_VERSION '2.17.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.17.0'.
❌ Makefile introduces PKG_VERSION '2.13.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.13.0'.
❌ Makefile introduces PKG_VERSION '2.13.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.13.0'.
❌ Makefile introduces PKG_VERSION '1.44', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.44'.
❌ Makefile introduces PKG_VERSION '0.36', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.36'.
❌ Makefile introduces PKG_VERSION '1.102.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.102.2'.
❌ Makefile introduces PKG_VERSION '3.7.8', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.7.8'.
❌ Makefile introduces PKG_VERSION '7.0.29', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 7.0.29'.
❌ Makefile introduces PKG_VERSION '4.14.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 4.14.2'.
❌ Makefile introduces PKG_VERSION '3.7.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.7.2'.
❌ Makefile introduces PKG_VERSION '26.3', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 26.3'.
❌ Makefile introduces PKG_VERSION '4.0.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 4.0.2'.
❌ Makefile introduces PKG_VERSION '1.31.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.31.0'.
❌ Makefile introduces PKG_VERSION '10.2.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 10.2.1'.
❌ Makefile introduces PKG_VERSION '3.1.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.1.0'.
❌ Makefile introduces PKG_VERSION '7.35.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 7.35.1'.
❌ Makefile introduces PKG_VERSION '2026.6.3', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2026.6.3'.
❌ Makefile introduces PKG_VERSION '1.4.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.4.1'.
❌ Makefile introduces PKG_VERSION '84.0.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 84.0.0'.
❌ Makefile introduces PKG_VERSION '1.13.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.13.0'.
❌ Makefile introduces PKG_VERSION '2.2.4', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.2.4'.
❌ Makefile introduces PKG_VERSION '4.24.5', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 4.24.5'.
❌ Makefile introduces PKG_VERSION '2.1.3', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.1.3'.
❌ Makefile introduces PKG_VERSION '3.12.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.12.1'.
❌ Makefile introduces PKG_VERSION '6.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 6.1'.
❌ Makefile introduces PKG_VERSION '3.18.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.18.0'.
❌ Makefile introduces PKG_VERSION '0.95.3', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.95.3'.
❌ Makefile introduces PKG_VERSION '2.3.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.3.1'.
❌ Makefile introduces PKG_VERSION '1.2.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.2.1'.
❌ Makefile introduces PKG_VERSION '0.41.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.41.1'.
❌ Makefile introduces PKG_VERSION '1.43.67', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.43.67'.
❌ Makefile introduces PKG_VERSION '1.43.67', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.43.67'.
❌ Makefile introduces PKG_VERSION '0.19.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.19.2'.
❌ Makefile introduces PKG_VERSION '8.8.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 8.8.0'.
❌ Makefile introduces PKG_VERSION '1.39.3', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.39.3'.
❌ Makefile introduces PKG_VERSION '7.1.0.2026080300', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 7.1.0.2026080300'.
❌ Makefile introduces PKG_VERSION '2.7.6', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.7.6'.
❌ Makefile introduces PKG_VERSION '2.0.0.1584', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.0.0.1584'.
❌ Makefile introduces PKG_VERSION '3.12.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.12.0'.
❌ Makefile introduces PKG_VERSION '1.4.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.4.1'.
❌ Makefile introduces PKG_VERSION '4.3.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 4.3.1'.
❌ Makefile introduces PKG_VERSION '4.11.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 4.11.1'.
❌ Makefile introduces PKG_VERSION '1.6.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.6.0'.
❌ Makefile introduces PKG_VERSION '0.52.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.52.1'.
❌ Makefile introduces PKG_VERSION '5.16.4', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 5.16.4'.
❌ Makefile introduces PKG_VERSION '9.1.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 9.1.1'.
❌ Makefile introduces PKG_VERSION '1.7.5', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.7.5'.
❌ Makefile introduces PKG_VERSION '26.2.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 26.2.1'.
❌ Makefile introduces PKG_VERSION '1.46.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.46.0'.
❌ Makefile introduces PKG_VERSION '1.4.4', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.4.4'.
❌ Makefile introduces PKG_VERSION '8.4.2', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 8.4.2'.
❌ Makefile introduces PKG_VERSION '2.1.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 2.1.1'.
❌ Makefile introduces PKG_VERSION '3.2.9', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.2.9'.
❌ Makefile introduces PKG_VERSION '3.5.4', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 3.5.4'.
❌ Makefile introduces PKG_VERSION '1.27.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.27.1'.
❌ Makefile introduces PKG_VERSION '0.70.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.70.1'.
❌ Makefile introduces PKG_VERSION '0.410', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.410'.
❌ Makefile introduces PKG_VERSION '0.6.4', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.6.4'.
❌ Makefile introduces PKG_VERSION '4.16.0', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 4.16.0'.
❌ Makefile introduces PKG_VERSION '1.0.13', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.0.13'.
❌ Makefile introduces PKG_VERSION '1.13.18', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 1.13.18'.
❌ Makefile introduces PKG_VERSION '0.1.1', but this version string is missing in the commit subject line. Please mention the new version in the subject, e.g. ': update to 0.1.1'.

Package Release Audit:

⚠️ Warning: Content changed in these packages, but without a PKG_RELEASE or version bump: net/nlbwmon
⚠️ Warning: Increment PKG_RELEASE by 1 (or bump PKG_VERSION/PKG_SOURCE_DATE and reset PKG_RELEASE to 1) so users receive the update.
ℹ️ Do not increment release for minor changes. Cosmetic edits (e.g., typos in comments, copyright updates, formatting/whitespace), changing the package maintainer (PKG_MAINTAINER), or updating source download info (PKG_SOURCE_URL / PKG_HASH) do not require incrementing PKG_RELEASE.

View more details on OpenWrt