-
Notifications
You must be signed in to change notification settings - Fork 221
Open
Labels
Description
We’ve begun running BotBrowser in production and appreciate the frequent updates. However, our Docker/CI builds currently hard-code GitHub release asset URLs. When asset filenames/paths advance, builds start failing with 404 Not Found until we manually change the Dockerfile. A small installer CLI (e.g., botbrowser install) that resolves the latest compatible build would eliminate this fragility.
Current behavior
Example of what breaks today (asset name/date changes → 404 in CI):
# Fails when the exact asset URL changes
RUN wget https://github.com/botswin/BotBrowser/releases/download/v141-20250927/botbrowser_20250928_141.0.7390.30_x86_64.deb
# the next day we have to switch to:
RUN wget https://github.com/botswin/BotBrowser/releases/download/v141-20250927/botbrowser_20250929_141.0.7390.30_x86_64.deb
Impact
- CI instability due to rotating asset names/paths
- Manual edits to Dockerfiles to unblock builds
- Avoidable failures when releases move quickly
Proposal: CLI for Docker/CI
Provide a lightweight, non-interactive installer that selects and installs the correct Linux/x86_64 asset without knowing the exact filename. Example:
# Latest stable for linux/x86_64, install .deb inside Docker
botbrowser install --channel stable --format deb --arch x86_64 --install