Fix large GitHub release JSON handling

2026-10-11 21:23:08 +07:00
parent aa4c241f99
commit 8f84934c46
2 changed files with 49 additions and 16 deletions
@@ -57,3 +57,11 @@ At 09:00 server-local time:
 ```

 Run the monitor under a dedicated user where possible. Keep `.env` private and do not commit it. Use `./monitor.sh --test-telegram` to verify Telegram and proxy connectivity.
+
+### Large release histories
+
+GitHub response pages are processed through temporary files, rather than passed
+through command-line arguments. The state file is read directly by `jq`.
+This prevents `Argument list too long` for repositories with large release notes.
+
+Run `bash -n monitor.sh` and `./monitor.sh --dry-run --verbose` to verify.