ilml-plugin-linkedin 1.20.26 → 1.20.27

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 1.20.27
+- **Fixed: Easy Apply often failed at the final review step because Yes/No questions (work authorization, visa sponsorship, relocation, hybrid/on-site) weren't being answered.** LinkedIn switched these questions from its old custom controls to standard radio buttons, which the form-filler no longer recognised — so it left the required question blank, the form wouldn't submit, and the whole application was skipped. In recent runs this was failing a large share of applications. The filler now reads the standard radio layout — pulling the question text and the Yes/No choices — and selects the answer, so these applications go through. It still answers a question only when it can clearly read both the question and its options; otherwise it skips it exactly as before, so no application ever gets a guessed answer.
+- The stuck-form log now captures the full field details (question, options, surrounding markup) so a future form change is faster to pin down.
+- No schema change.
+
 ## 1.20.26
 - **Discovered people now use one consistent `title` field — and your existing pool is repaired on upgrade.** The discovery pool had drifted to two names for the same thing (the position line under a person's name): some records used `title`, others `headline`. Worse, the pre-1.20.25 side-panel bug had glued names to the badge + position ("Jane Doe· 3rd+Head of Talent…"). On upgrade a one-time migration cleans discovered-people.json: it de-glues the names and moves every `headline` into `title`, so each record carries a single, clean `title` (matching the rest of your contacts). Your data file is backed up automatically first, and the fix is safe to re-run. In practice this makes the accumulated pool searchable again — e.g. the investors you'd harvested but couldn't tell apart now show up by title. Going forward the harvest writes `title` directly.
 - No data lost — a field is renamed/relocated, not dropped.