ilml-plugin-linkedin 1.20.16 → 1.20.18

package/CHANGELOG.md

@@ -1,4 +1,12 @@
 # Changelog
+2
+## 1.20.18
+- **`apply` now decides "already applied?" purely from what LinkedIn shows, not from its own past records.** Until now the plugin also skipped a job whenever its local record said "applied" — but that record could be wrong (an earlier version's misfiring badge-check wrote false "applied" marks), and those stale marks then made `apply` skip fresh jobs it had never touched, quietly wasting a run's quota. `apply` now treats LinkedIn's own signals — the "Applied" badge on each search-results card and the status on the open job — as the only word on whether you've already applied. Its local record is still used to skip jobs *you* couldn't complete (a form it can't fill, a job that won't open), which LinkedIn can't tell it about; and it still keeps a record of everything for reporting.
+- No schema change.
+
+## 1.20.17
+- **Fixed: `apply` again skipped every job as "already applied" on one of LinkedIn's two job layouts.** LinkedIn A/B-serves two different job UIs that can switch between browsers/sessions, and each marks the search-results cards differently. The 1.20.16 fix taught the "already applied" check to recognise one layout's cards but, in doing so, stopped recognising the other's — so on that layout every job again read as already applied and a run submitted nothing. The check now recognises the results list in BOTH layouts, so the "Applied" badges on other jobs are ignored on whichever UI you're served, and only the job you're actually on is counted. (The 1.20.16 safety net stays: if the check ever misfires anyway, `apply` distrusts it for the rest of the run and falls back to its own record instead of skipping everything.)
+- No schema change.
 
 ## 1.20.16
 - **Fixed: `apply` stopped submitting applications — it skipped almost every job as "already applied".** LinkedIn's new job UI dropped an internal attribute the plugin used to tell the left-hand results list apart from the open job, so `apply` mistook the "Applied" badges on OTHER jobs in that list for the open job and skipped brand-new jobs as if you'd already applied — a whole run could end up applying to nothing. It now identifies the results list by its current markers, so the "already applied" check reads only the job you're actually on.