From 4b9ba083dd82f774dab91ced6bdbbb54cec3ff17 Mon Sep 17 00:00:00 2001 From: luisleo526 Date: Mon, 5 Oct 2026 13:41:22 +0800 Subject: [PATCH] docs: run the symbol-feeds example on the 1.2.0 image The README's other-symbols example ran pineforge-release:1.1.0. Release 1.2.0 is published (ghcr.io/pineforge-4pass/pineforge-release:1.2.0, also tagged 1.2 and latest) and keeps the PINEFORGE_SYMBOL_FEEDS harness, whose docker/run_json.py is byte-identical to 1.1.0's; the lines saying the feature arrived in 1.1.0 stay. Co-Authored-By: Claude Opus 5.5 (1M context) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4767cca..6b4911e 100644 --- a/README.md +++ b/README.md @@ -98,7 +98,7 @@ docker run --rm \ -v $(pwd)/btcusdt-240.csv:/in/ohlcv.csv:ro \ -v $(pwd)/symbols:/in/symbols:ro \ -e PINEFORGE_SYMBOL_FEEDS=/in/symbols/symbols.json \ - ghcr.io/pineforge-4pass/pineforge-release:1.1.0 > report.json + ghcr.io/pineforge-4pass/pineforge-release:1.2.0 > report.json ``` - A key is the exact string the script passes at run time, exchange prefix and