node-red-contrib-modbus-modpackqt 2.0.3 → 2.0.5

package/CHANGELOG.md

@@ -4,6 +4,23 @@ All notable changes to **node-red-contrib-modbus-modpackqt** are documented
 here. This project follows [Semantic Versioning](https://semver.org/) — pin a
 major version (`^2.0.0`) in production.
 
+## [2.0.5] — 2026-05-09
+
+### Changed
+
+- **README:** removed the "Why Modbus + bytes are split into two palettes"
+  explainer section.
+
+## [2.0.4] — 2026-05-09
+
+### Changed
+
+- **README & package.json:** removed all GitHub repo and email references
+  (we don't have a public GitHub org or support inbox set up yet). Bug reports
+  and security disclosures now go through `modpackqt.com/contact` and
+  `modpackqt.com/security`. The `repository` field was removed from
+  package.json since the URL was a placeholder.
+
 ## [2.0.3] — 2026-05-09
 
 ### Changed

package/README.md

@@ -146,18 +146,6 @@ External masters connecting to `your-host:1502`, unit `1`, FC `3`, address `0`,
 
 ---
 
-## Why Modbus + bytes are split into two palettes
-
-Most Modbus packages bake type decoding into the read node — one giant dropdown for int16 / int32 / float32 / Siemens-CDAB / etc. That made sense in 2010 but it's a mess: every protocol re-implements the same decoders, and you can't reuse them for MQTT / TCP / BLE / file payloads.
-
-We split them on purpose:
-- **Modbus nodes** speak Modbus and output raw registers — nothing else.
-- **Bytes nodes** decode any binary payload into typed values.
-
-You write less code, your flows stay readable, and the same decoder works whether the data came from a PLC, an MQTT broker, or a UDP socket.
-
----
-
 ## Pricing
 
 | | Free | Paid |
@@ -202,17 +190,14 @@ Make sure `node-red-contrib-bytes-modpackqt` is also installed before importing
 
 ## Reporting bugs & getting updates
 
-- **Bugs / feature requests:** open a GitHub issue at the repository linked in
-  `package.json`, or email **support@modpackqt.com**.
-- **Security issues:** see [`SECURITY.md`](./SECURITY.md) — please report
-  privately to **support@modpackqt.com**.
+- **Bugs / feature requests:** use our [contact page](https://modpackqt.com/contact).
+- **Security issues:** report privately via the [security page](https://modpackqt.com/security).
 - **Updates are never automatic.** Node-RED's palette manager will show
   "update available" when we publish a new version — you choose when to
   upgrade. Pin a major version (`^2.0.0`) in production.
-- **Changelog:** see [`CHANGELOG.md`](./CHANGELOG.md). We follow
-  [semver](https://semver.org/) — patch releases for bug fixes only.
-- **Paid customers** get email notice for security and breaking-change
-  releases.
+- **Changelog:** the `CHANGELOG.md` file is shipped inside this package. We
+  follow [semver](https://semver.org/) — patch releases for bug fixes only.
+- **Paid customers** get notice for security and breaking-change releases.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "node-red-contrib-modbus-modpackqt",
-  "version": "2.0.3",
+  "version": "2.0.5",
   "description": "Node-RED Modbus nodes — embedded Modbus TCP/RTU master + slave server, no extra apps required. By ModPackQT. FC1/FC2/FC3/FC4 reads, FC5/FC6/FC15/FC16 writes, a built-in slave register store, and a free passive traffic monitor for debugging.",
   "keywords": [
     "node-red",
@@ -22,13 +22,8 @@
   "license": "MIT",
   "author": "ModPackQT",
   "homepage": "https://modpackqt.com/nodered",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/modpackqt/node-red-contrib-modbus-modpackqt.git"
-  },
   "bugs": {
-    "url": "https://github.com/modpackqt/node-red-contrib-modbus-modpackqt/issues",
-    "email": "support@modpackqt.com"
+    "url": "https://modpackqt.com/contact"
   },
   "engines": {
     "node": ">=14"