This release fixes issues for SREs watching stability and regressions.
✓ No known CVEs patched in this version
Topics
+3 more
Summary
AI summaryFixed LinkedIn post scraping after its May 2026 React migration, restored correct author/text/comments.
Full changelog
Fixes
- core: Rewrite `get-post` DOM scrapers for LinkedIn React/SDUI post-detail (#800) — restore correct author/text/comments after LinkedIn's 2026-05-06 migration to React + CSS Modules + SDUI. Legacy scrapers were silently falling through to the Premium upsell banner, producing `authorName: "Premium"`, empty `text`, and empty `comments` while top-level counts remained correct. New SDUI selectors scope by `[componentkey^="expanded"][componentkey$="FeedType_FEED_DETAIL"]` (verified across regular, share-, ugcPost-, and self-authored posts). Adds 14-entry UI-string blocklist as semantic regression guard.
- mcp: Forward `accountId` from tool handlers to core operations across 53 wrappers — multi-account users could not target a specific instance via the MCP layer (e.g. `campaign-list` with `accountId` failed with `AccountResolutionError: Multiple accounts found` because `accountId` was destructured out and silently dropped). Adds shared `describeAccountIdForwarding` test helper with Zod `safeParse` validation to prevent silent drift, plus per-tool regression tests for all 53 fixed wrappers.
- test: Extend timeout for monitor-collecting-saga timeout-state assertion (#801) — Ubuntu CI flake from 1 ms millisecond-quantization race in `while (Date.now() < deadline)` evaluation. Extended to 50 ms; `pollInterval: 1` preserved (delay is mocked).
Full Changelog: https://github.com/alexey-pelykh/lhremote/compare/v0.20.0...v0.20.1
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About alexey-pelykh/lhremote
Open-source CLI and MCP server for LinkedHelper automation — 32 tools for campaign management, messaging, and profile queries via Chrome DevTools Protocol.
Related context
Beta — feedback welcome: [email protected]