# Changelog of WeChat Article Detail Scraper — 公众号文章正文提取 (`opspilot.cc/wechat-article-detail-scraper`) Actor

- **URL**: https://apify.com/opspilot.cc/wechat-article-detail-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/opspilot.cc/wechat-article-detail-scraper.md

## Changelog

All notable changes to this Actor are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).

### \[0.1.0] - 2026-09-16

#### Verified

- Build: `0.1.1` (id `CXeuzFSgADb9GQk5O`) — Actor id `5vrr8dBcnclIva0Lx`.
- Live run: id `g6g3UykReGEkr6cIA`, status `SUCCEEDED`, 8.57 s, exitCode 0. Dataset item returned all expected fields (title / nickName / ghUsername / alias / publishTime / commentId / contentTextLength / contentTextTruncated / headImage).

#### Added

- Initial release.
- `fetch_article_detail` endpoint (default engine) returns full plain-text body, title, author, account identity, head image (round + HD), cover, album info, and `comment_id`.
- `fetch_article_detail_h5` endpoint variant exposed via `engine=h5` (faster but `alias` / head images are `null`).
- 64-bit `comment_id` always string-typed (JS-safe). `msgId` may be string or number depending on the upstream's actual payload length.
- Optional `maxContentChars` truncation (0 = no truncation, capped at 200000).
- Optional `rawData` attachment when `raw=true`.
- Free tier: 5 runs/day (Actor default KV store, gated by `APIFY_USER_IS_PAYING !== '1'`).
- Paid tier: per-result billing on `article-detail-result`.
- 30 unit-test assertions + 9 integration scenarios.
- Real-upstream smoke test verified (`code=200`, `contentText length=2998`, `comment_id=3884868893382230017`, `alias=QbitAI`).

#### Notes

- Per upstream docs the upstream takes ~30 s to respond; the Actor uses a 60 s client timeout (Apify automatic tests fail at 5 min, so any run that takes >5 min must use `raw=false` to keep the payload small).