From 321ad3fd5e14401528d8c455c4c5e4255a62a942 Mon Sep 17 00:00:00 2001
From: jehrr <79864894+jehrr@users.noreply.github.com>
Date: Fri, 9 Oct 2026 10:26:22 +0000
Subject: [PATCH] Release 0.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The audit of 8 October, worked end to end: the --mode events completion
semantics, the classifier that read every served page as its own 404, atomic
output writes, a live cross-engine canary and a digest-pinned base image —
plus two defects found while verifying those, and one regression of my own
found by running the README in a fresh clone.

Leads with a blockquote because the behaviour change is one an existing user
would otherwise discover from a row count: a --mode events walk that used to
stop early under a green status now returns the whole listing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---
 CHANGELOG.md   | 21 ++++++++++++++++++++-
 pyproject.toml |  2 +-
 2 files changed, 21 insertions(+), 2 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8abb844..37369e4 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,24 @@ from a row count, it leads the section in a blockquote.
 
 ## [Unreleased]
 
+## [0.2.0] — 2026-10-09
+
+A third-party audit of 8 October, worked end to end. All four of its findings
+were real. Investigating the first one found a second defect underneath it
+that the audit had not seen, and the two compounded: one was manufacturing
+the condition the other mistook for the end of a walk.
+
+> **If you use `--mode events`, this release changes what you get and what
+> the sidecar calls it.** A walk used to stop at the first event page that
+> produced no markets and still report `status: complete` with exit 0 — and
+> a separate defect was making healthy event pages produce no rows, so that
+> was a common case rather than an edge one. A walk that previously returned
+> a few pages' worth of markets under a green status now returns the whole
+> listing's. Expect row counts to rise sharply, expect `complete` to start
+> meaning what it says, and note that `no_new_products` is no longer a stop
+> reason this project emits.
+
+
 ### Fixed
 
 - **`events_on_page_1` under-reported the listing in `--mode events`.** The
@@ -487,6 +505,7 @@ Each of these was found by running the thing rather than by reading it (§15):
 - An issue template described two other sites at once.
 - `scraper_api_client.py` imported a parser function that no longer exists.
 
-[Unreleased]: https://github.com/2scraper/polymarket-scraper/compare/v0.1.1...HEAD
+[Unreleased]: https://github.com/2scraper/polymarket-scraper/compare/v0.2.0...HEAD
+[0.2.0]: https://github.com/2scraper/polymarket-scraper/compare/v0.1.1...v0.2.0
 [0.1.1]: https://github.com/2scraper/polymarket-scraper/compare/v0.1.0...v0.1.1
 [0.1.0]: https://github.com/2scraper/polymarket-scraper/releases/tag/v0.1.0
diff --git a/pyproject.toml b/pyproject.toml
index 5360799..fb3bb34 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "polymarket-scraper"
-version = "0.1.1"
+version = "0.2.0"
 description = "Polymarket prediction-market scraper: listings, categories, searches and event pages, with prices, order books, volumes and CLOB token ids."
 readme = "README.md"
 license = "MIT"