ilml-plugin-linkedin 1.18.1 → 1.19.1

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 1.19.1
+- **`connect run` now verifies each send actually went out before counting it.** After clicking "Send" (with or without a note) it confirms the invite modal actually closed and no error toast appeared — retrying the click once if the modal is still open — instead of assuming "probably sent" on a click timeout. Before this, a click that silently didn't register left the modal open yet still got logged as sent (you'd find an un-pressed "Send without a note" button sitting in the window). An unconfirmed send is now reported as a failure, not a false success. No schema change.
+
+## 1.19.0
+- **`connect run` now reaches people whose "Connect" is tucked under the "More" (⋯) menu** — the out-of-network profiles (often investors / senior folks) it used to silently skip as "already connected". Since 1.14.5 the plugin trusted the "· 1st" distance badge as proof of an existing connection, but that badge is unreliable and made it skip connectable targets without ever opening their "More" menu. Now whether you're connected is decided by the **actual Connect control** (found by the full search, including the "More" dropdown), never by the badge: a Connect control anywhere ⇒ send; none found ⇒ genuinely connected ⇒ clean skip.
+- **Safety hardening so this can't misfire.** The dropdown search can never select a "Remove connection" item (excluded everywhere); a click-time guard refuses any remove / disconnect / report / block / unfollow control; and the last-resort button strategies now exclude the "People you may know" recommendation rail and verify the name — so a same-first-name rail neighbour can't receive the request meant for your target. A safety refusal counts as a clean skip, not a failure, so it can't trip the run's circuit breaker. No schema change.
+
 ## 1.18.1
 - **Fixed: `connect run` skipped people you're NOT connected to as "already connected".** When a profile showed a real **Connect** button, a separate read of the "1st / 2nd / 3rd" distance badge could pick up a stray "1st" from elsewhere on the page and wrongly override the result to "already connected" — silently skipping valid targets without ever sending. Now a Connect button on the profile is authoritative proof you're not connected (LinkedIn never shows Connect for an existing connection); the distance badge is only a fallback used when neither a Connect nor a Message button is found. No schema change.