ilml-plugin-linkedin 1.20.5 → 1.20.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +6 -0
- package/dist/connect.mjs +70 -70
- package/dist/enrichProfile.mjs +15 -15
- package/dist/enrichProfiles.mjs +43 -43
- package/dist/funnelRunner.mjs +45 -45
- package/dist/messageBot.mjs +52 -52
- package/dist/readPost.mjs +10 -10
- package/dist/run.mjs +60 -60
- package/dist/scout.mjs +26 -26
- package/dist/syncAll.mjs +103 -103
- package/dist/syncConnections.mjs +45 -45
- package/dist/verifyAbout.mjs +17 -17
- package/dist/version.mjs +1 -1
- package/dist/viewers.mjs +37 -37
- package/dist/visit.mjs +32 -32
- package/ilml-plugin.json +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.20.7
|
|
4
|
+
- **Fixed: `messages --send-batch` crashed instead of sending.** The batch JSON's message body can now be either `text` or `message` — the `--draft-batch` command uses `text`, but `--send-batch` previously required `message` and, if you passed `text`, crashed with an unhelpful "Cannot read properties of undefined" instead of sending. Both batch commands now accept the same shape (`[{ "name": "...", "text": "..." }]`). An entry that's missing its message body is now reported as a clear per-entry error and skipped, instead of aborting the whole batch. No schema change.
|
|
5
|
+
|
|
6
|
+
## 1.20.6
|
|
7
|
+
- **Every command that opens LinkedIn now waits through the ~30-second "signing you back in" screen — not just `apply`, `connect` and `sync`.** 1.20.4–1.20.5 taught those commands to wait through LinkedIn's re-verification screen (the one that shows up when you've recently signed in from another location or device) instead of mistaking it for a logout. This release extends the same handling to the rest of the commands that load a page: `sync-connections`, `viewers`, `read-post`, `enrich --with-experience`, and the profile fallback used when sending a message. Before, these could fail or come back empty during that screen — `sync-connections` in particular looked for a login redirect too early (after about 3 seconds) and then waited only 15, so a slow re-verify looked like "not logged in". Now they all wait up to 45 seconds and only report a session problem if a real login page is still showing afterwards. Under the hood this is now one shared piece of logic rather than the same sequence repeated in each command, so coverage stays consistent as new commands are added. No schema change.
|
|
8
|
+
|
|
3
9
|
## 1.20.5
|
|
4
10
|
- **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.
|
|
5
11
|
|