ilml-plugin-linkedin 1.11.0 → 1.11.2

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 1.11.2
+- **Plugin loads again when installed via `ilml plugin install linkedin`.** v1.11.0 introduced a transitive dependency (`debug` via Puppeteer's stealth plugin) that uses `require('tty')` at runtime — esbuild can't bundle dynamic CommonJS requires into an ESM module, so any `ilml linkedin <command>` died on startup with `Dynamic require of "tty" is not supported`. The build now uses `packages: 'external'` to keep all `node_modules` deps unbundled at runtime (installed by npm into the plugin directory as usual). Same install footprint, no schema change — just the bundle behaves correctly.
+- No schema migration; existing data files unchanged.
+
+## 1.11.1
+- **`sync-all` now backfills profile URLs for card-only stub conversations.** When the inbox scan saw a conversation card but never successfully opened its thread (e.g. an earlier sync failed mid-read, or the thread was created from outbound activity alone), the entry was stuck with 0 stored messages and no `profileUrl` — and the previous "re-read to capture URL" check required `messages.length > 0`, so these stubs were never picked up again. The condition now triggers re-read on any sign of activity (stored messages OR sidebar preview), so empty-but-recently-active stubs are queued for thread-open on the next sync. Net effect on long-running databases: dozens of conversations that had only sidebar metadata get their profile URL and message body filled in over the next few sync passes. Backwards-compatible — only adds re-read attempts that previously weren't made.
+- No schema migration; existing data files unchanged.
+
 ## 1.11.0
 - **`sync-all` no longer gives up when a single thread misbehaves.** LinkedIn's inbox occasionally reacts to an automated search input by navigating the page away from `/messaging/` mid-sync. In v1.10.0 that single navigation killed the entire remaining queue — the run would abort on, say, item 1 of 67 and silently leave 66 unread. The thread loop now treats both thrown exceptions and verified-false returns the same way: log it, hand the thread to the sidebar fallback below, and keep moving. A bad thread costs that one slot, not the whole sync.
 - **`sync-all` now reaches conversations buried deep in the inbox.** LinkedIn only renders ~20 sidebar cards at a time and lazy-loads the rest on scroll. Older threads — including any conversation that hadn't received a recent message — sat outside that initial window, so the existing "click the card in the sidebar" path couldn't find them. When that fails, the sync now navigates back to `/messaging/`, scrolls the sidebar from the top, and reopens the thread once its card has been loaded. The happy path (top-of-inbox conversations found by direct click) is unchanged — only previously-failing threads pay the extra scrolling time.