From decfc6bb6eb10a29ed6aaabb07244b8915042604 Mon Sep 17 00:00:00 2001 From: semantic-release-bot Date: Fri, 21 Aug 2026 08:21:39 +0000 Subject: [PATCH 1/8] ci(release): 2.2.0-beta.7 [skip ci] ## [2.2.0-beta.7](https://github.com/ScrapeGraphAI/Scrapegraph-ai/compare/v2.2.0-beta.6...v2.2.0-beta.7) (2026-08-21) ### Bug Fixes * resolve markdown links from the document URL ([875385b](https://github.com/ScrapeGraphAI/Scrapegraph-ai/commit/875385b56a3b2ce33b0bddc7baa194017d0293e2)) ### Docs * fix timeout documentation links ([4763fdc](https://github.com/ScrapeGraphAI/Scrapegraph-ai/commit/4763fdcc08af079a7e5a386ce58e7ae2d989155d)) --- CHANGELOG.md | 12 ++++++++++++ pyproject.toml | 2 +- 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 6c08454ac..7b6793442 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,15 @@ +## [2.2.0-beta.7](https://github.com/ScrapeGraphAI/Scrapegraph-ai/compare/v2.2.0-beta.6...v2.2.0-beta.7) (2026-08-21) + + +### Bug Fixes + +* resolve markdown links from the document URL ([875385b](https://github.com/ScrapeGraphAI/Scrapegraph-ai/commit/875385b56a3b2ce33b0bddc7baa194017d0293e2)) + + +### Docs + +* fix timeout documentation links ([4763fdc](https://github.com/ScrapeGraphAI/Scrapegraph-ai/commit/4763fdcc08af079a7e5a386ce58e7ae2d989155d)) + ## [2.2.0-beta.6](https://github.com/ScrapeGraphAI/Scrapegraph-ai/compare/v2.2.0-beta.5...v2.2.0-beta.6) (2026-08-19) diff --git a/pyproject.toml b/pyproject.toml index 20e58930d..051608dd3 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -1,7 +1,7 @@ [project] name = "scrapegraphai" -version = "2.2.0b6" +version = "2.2.0b7" description = "A web scraping library based on LangChain which uses LLM and direct graph logic to create scraping pipelines." authors = [ From f91478eacf86485f6b9efcf843fc0c815dde1ec5 Mon Sep 17 00:00:00 2001 From: Marco Vinciguerra Date: Sun, 23 Aug 2026 15:11:48 +0200 Subject: [PATCH 2/8] fix(fetch): surface HTTP errors and missing content instead of answering NA MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A page that could not be scraped as intended was indistinguishable from one that could. FetchNode's default path (ChromiumLoader -> ascrape_playwright) dropped the Response returned by page.goto(), so a 404, 403, 500, captcha wall or login redirect reached the LLM as ordinary content and the model answered "NA" with nothing in the logs to explain why. Reported in #1102, where en.wikipedia.org/wiki/Timpson_(company) 404s (the article is at Timpson_(retailer)) and the run still looked clean. Two deterministic, LLM-free guards, both warnings so existing behaviour is unchanged for anyone deliberately scraping error pages: - ChromiumLoader keeps the Response from every page.goto() call site (ascrape_playwright, ascrape_playwright_scroll, ascrape_with_js_support) and warns on status >= 400. This mirrors what the opt-in use_soup=True path in FetchNode has always done. - ParseNode warns when the parsed content contains none of the terms the user asked about — schema field names plus the significant words of the prompt. A 200 response can still reach the LLM without the requested data: content behind JavaScript that never rendered, a field inside a