ilml-plugin-linkedin 1.20.9 → 1.20.11

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## 1.20.11
+- **Fixed: `read-post` reported "Auth wall — cookies expired or not logged in" on a post you could actually open — even while every other command was signed in on the same account.** Opening a post by its direct link lands on LinkedIn's brief "signing you back in" screen more often than an in-app click does, and `read-post` decided too early that you'd been logged out, with no attempt to recover. It now waits through that screen and self-heals the same way the other commands do (reopens your feed to refresh the session, then retries the post), so a valid session reads the post instead of failing. It only reports a real sign-in problem if the wall is still up after recovery.
+- **Fixed (Windows): a `read-post` that hit that sign-in wall could leave a hidden browser open that blocked your next command.** On the way out it force-closed its browser in a way that doesn't work on Windows, so the browser stayed running and held the automation profile — and the next command failed with "another LinkedIn automation command is already running". `read-post` now closes its browser cleanly before it exits.
+- **Fixed: `scout` aborted the whole run with "session expired" the moment LinkedIn showed its sign-in wall on a job search — even when your session was still good.** Job-search links trigger that wall more readily than other pages, and `scout` gave up instantly instead of recovering. It now self-heals the same way the rest of the plugin does (refresh via your feed, then return to the search) before concluding you're signed out, and only stops if it genuinely can't get back in.
+- No schema change.
+
+## 1.20.10
+- **Fixed: `messages --push-drafts` could report a message as "sent" without actually delivering it.** When the draft's thread was already open in your inbox, the send ran on the shared messaging page and could land on the WRONG message box — a leftover floating chat bubble for a different person — then see that box clear and report "✓ sent" while the intended person received nothing. Push now prefers the reliable path that opens the recipient's own profile and confirms the recipient before sending (the same path `--send` has used since 1.17.2, which the draft push never actually adopted), and only falls back to the inbox path when no profile link is on file. A send that can't be confirmed is now reported as "failed" (your draft is kept) instead of a false "sent". Under the hood, the "did it actually send?" check is now one shared piece of logic used by both send paths, so it can't drift out of sync between them again.
+- **Fixed: `messages --send "First Last" "text"` no longer sends a garbled fragment when the name or message contains spaces.** A quoted multi-word argument can get split on spaces before the plugin sees it, which could turn `--send "Jane Doe" "hi there"` into sending just a stray word. `--send` now detects the split and refuses with a clear message pointing you to the file-based form (`--send-batch @file.json`, or `--draft-batch @file.json` → `--push-drafts`), instead of delivering garbage.
+- No schema change.
+
 ## 1.20.9
 - **Commands now recover on their own when LinkedIn puts up its sign-in wall mid-run — instead of stopping and making you start over.** LinkedIn periodically throws its "join / sign in" screen on a page even though your session is still good (common when you've recently signed in from another device or location). Until now that ended the command with "session expired", and you had to log in again and re-run it. Now, when a command hits that wall, it quietly reopens your feed — where LinkedIn usually recognises you from your existing session within a few seconds, no password needed — refreshes your saved sign-in, and continues where it left off, hands-free. If LinkedIn genuinely asks for your email and password (a real sign-out), the command pauses and waits while you sign in **in the browser window it already has open**, then resumes on its own — no need to close anything or run the command again. Safeguards: your saved session is only overwritten when the refreshed one is actually valid, so a half-loaded page can never replace a good login; and an unattended/scheduled run won't hang waiting for a sign-in nobody can complete — it fails fast with a clear message instead. This works the same way across every command. No schema change.