fix(binance-trading-bot): unbreak build — pip PEP 668 + v1.0.0 (#2945)

* fix(binance-trading-bot): pip install with --break-system-packages (PEP 668)

Alpine's py3-pip now marks the system Python as externally managed, so the
TradingView requirements install failed with 'externally-managed-environment'
and broke every rebuild (run 31227083872).

Also bumps to upstream v1.0.0, which the updater bot tried and had reverted by
the same build failure.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(binance-trading-bot): pin base image to the frozen v0 line, drop the v1.0.0 bump

Upstream retagged chrisleekr/binance-trading-bot:latest to v1.0.0 on 2026-07-31
(latest and v1.0.0 share digest sha256:60a1a88e...). build.json pinned :latest,
so this add-on was silently building on the v1 rewrite while its rootfs still
starts mongod/redis and runs the v0 'npm start' entrypoint.

v1.0.0 is a complete rewrite with no in-place upgrade: the datastore moved to
Postgres + TimescaleDB. Adopting it needs an add-on rewrite, not a version bump,
so pin build_from to :0.0.101 (the frozen v0 line, linux/amd64 + linux/arm64)
and pause the updater so the bot stops re-proposing v1 weekly.

Keeps --break-system-packages so the build survives PEP 668 if the pin ever
moves forward.

Reported by Copilot on PR #2945.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(binance-trading-bot): drop --break-system-packages, the pinned image predates it

CI: 'no such option: --break-system-packages'. The 0.0.101 image ships a pip
older than 23.0.1, which is where that flag was introduced.

The flag was only ever needed because :latest had moved to the v1 rewrite and
its newer Alpine carries a PEP 668 marker. With build_from pinned to the frozen
0.0.101 image, that marker cannot appear, so the flag is both unnecessary and
fatal. binance-trading-bot/Dockerfile is now identical to master again: the
whole fix is the build.json pin.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

binance-trading-bot/CHANGELOG.md

@@ -1,3 +1,8 @@
+## 0.0.101.1 (2026-08-08)
+- Fix broken builds: upstream retagged `:latest` to the v1.0.0 rewrite on 2026-07-31, so this add-on was building on an image its rootfs does not support. `build_from` is now pinned to `chrisleekr/binance-trading-bot:0.0.101`, the frozen v0 line this add-on targets.
+- This also resolves the `externally-managed-environment` (PEP 668) pip failure, which was a symptom of the same retag: the v1 image ships a much newer Alpine than the v0 line this add-on is built against.
+- Upstream tracking is paused: v1.0.0 is a complete rewrite with no in-place upgrade (datastore moved to Postgres + TimescaleDB), so it needs an add-on rewrite rather than a version bump.
+
 - Added support for configuring extra environment variables via the `env_vars` add-on option alongside config.yaml. See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
 
 ## 0.0.101 (2025-06-13)

binance-trading-bot/build.json

@@ -1,6 +1,6 @@
 {
   "build_from": {
-    "aarch64": "chrisleekr/binance-trading-bot:latest",
-    "amd64": "chrisleekr/binance-trading-bot:latest"
+    "aarch64": "chrisleekr/binance-trading-bot:0.0.101",
+    "amd64": "chrisleekr/binance-trading-bot:0.0.101"
   }
 }

binance-trading-bot/config.yaml

@@ -115,4 +115,4 @@ schema:
 slug: binance-trading-bot
 udev: true
 url: https://github.com/alexbelgium/hassio-addons
-version: 0.0.101
+version: 0.0.101.1

binance-trading-bot/updater.json

@@ -1,6 +1,7 @@
 {
   "github_beta": "true",
-  "last_update": "13-06-2025",
+  "last_update": "08-08-2026",
+  "paused": true,
   "repository": "alexbelgium/hassio-addons",
   "slug": "binance-trading-bot",
   "source": "github",