version-tracker-daily-check

Run python3 checkers/runner.py from the version-tracker directory. The runner sequentially checks every enabled version_source row that is due, using only the Python standard library, and writes results to the SQLite database.

Builtin checkers cover github, github_release, rss, api (JSON), and css_selector sources. Custom checkers can be added as Python modules in checkers/custom/ and are loaded dynamically via importlib based on the source's check_method.

Use a cron schedule such as 0 */6 * * * that invokes the runner, then query version_change_event WHERE research_status='new' to report what changed. The database path can be overridden with the VERSION_TRACKER_DB environment variable.

The runner records a failed check_run, increments consecutive_failures, and consults the error_classification table. Once failures exceed max_retries, it disables the source, triggers re-discovery, or files a research_note for human review depending on the error code.

No. BOT_WALL and CAPTCHA_GATE errors disable the source and file a research_note for human triage. The documented guidance is to find an official feed or API, check manually, or drop the source rather than proxying around the wall.

The runner is sequential by design, acting as a single writer against the SQLite database. Many sources mean long runtime, so the documentation recommends starting with a small set of sources.