ilml-plugin-linkedin 1.14.2 → 1.14.4

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 1.14.4
+- **`connect run` now recognises people you're already connected to (or already have a pending request with) and skips them cleanly — instead of logging a false failure.** When a queued person is already a 1st-degree connection, their profile shows "Message" and no "Connect" — but the "More profiles for you" sidebar has its own Connect controls, which made connect think a Connect button was still present, miss that you're already connected, and record a `button_not_found` "failure". The already-connected / already-pending check now ignores that sidebar and reads only the open profile, so such entries are marked **skipped (already connected)** instead of failed: they don't count toward the "3 failures in a row" safety stop and don't burn quota. It stays conservative about writing anything back to your contacts — a real send is recorded, but a merely-inferred "already connected" only refreshes a person you already have, it won't invent a connection for an unknown profile (the source of truth for who you're connected to remains `sync`). Net effect — the failure list holds only real problems. Same root cause as 1.14.3 (recommendation-sidebar bleed), applied to status detection. No schema change.
+
+## 1.14.3
+- **`connect run` no longer sends the request to the wrong person.** On some profiles — typically well-known people you're not connected to, whose own "Connect" is tucked under the "More" menu — LinkedIn shows a "More profiles for you" sidebar where each suggested person has their own Connect control. Connect could grab the first of those sidebar controls and send the request to that person instead of the profile you queued, while the log still reported your intended target as sent (and your quota was spent on it). Connect now acts only on the Connect control that belongs to the open profile: it ignores the recommendation sidebar, and as a final check refuses to click any "Invite X to connect" control whose name doesn't match the profile it's on — a mismatch is skipped (and your quota left intact) rather than sent to the wrong person. This was a long-standing latent issue that only surfaced on profiles without their own inline Connect button. No schema change.
+
 ## 1.14.2
 - **`connect fill` now validates that a person's title actually matches the category before queueing them.** The `category` on your contacts is set automatically and is sometimes wrong (e.g. a "Software Developer" tagged `founder`), which meant `fill --category=founder` could queue the wrong people. `fill` now re-checks each person's stored title against the category and drops the ones that don't match; people with no stored title are held rather than queued (it never visits a profile to fetch one, so there's no added ban risk). Pass `--no-validate` for the old behaviour. The summary shows how many were filtered.