ilml-plugin-linkedin 1.20.3 → 1.20.5

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 1.20.5
+- **Fixed: `apply` and `connect` no longer fail when LinkedIn briefly re-verifies your sign-in.** LinkedIn sometimes shows a ~30-second "signing you back in" screen before opening the page you asked for — especially if you've recently signed in from a different location or device (e.g. your phone abroad while the tool runs on your desktop). Your session is still valid; LinkedIn is just re-checking. The plugin used to read the page before that finished and mistake it for a logout — `apply` stopped with "session expired", and `connect run` saw no Connect button and counted it as a failure (tripping its safety stop after a few in a row). Now these commands wait through that screen (up to 45 seconds) and only ask you to sign in again if a real login page is still showing afterwards. (1.20.4 fixed the same thing for `sync`; this extends it to `apply` and `connect`.) No schema change.
+
+## 1.20.4
+- **Fixed: commands no longer fail while LinkedIn is still showing its "setting things up" loading screen.** LinkedIn now often shows a roughly 30-second initialization screen and only then redirects to the page you asked for. The plugin used to give up before that finished — which showed up as false "not logged in / redirected to login" errors on sync, a message box that "never appeared" when sending, and hit-or-miss inbox searches. Every command now waits through that loading screen (up to 45 seconds) before deciding anything, so a slow LinkedIn load no longer looks like a failure. No schema change.
+
 ## 1.20.3
 - **Fixed: an interrupted or crashed run no longer leaves a hidden browser open that blocks your next command.** Before, if a command was interrupted (Ctrl-C), hit an error, or had its output piped to something that closed early, its automation browser could stay running in the background — and the next `connect` / `sync` / `apply` would then fail with a "the profile is already open" error. Two layers now prevent this:
   - Every command reliably closes its own browser when it exits — on normal finish, Ctrl-C, termination, an uncaught error, or a closed output pipe.