Version 3.11.1

3.11.1 has no new features. It fixes eight defects found in the days after 3.11.0 shipped, most of them things that quietly did nothing rather than things that visibly broke.

Your feed

• The same job found twice is now one listing. A job discovered by two different searches was landing in your feed twice whenever the two searches described its location differently. "Chicago, IL" and "Chicago, Illinois" were treated as different places, so the duplicate check never fired. They are now resolved to the same place before the comparison, along with the other spellings, abbreviations and accented forms that behaved the same way.
• Two more ways a job could sit unscored are closed. A listing that arrived with no description — from a source that gives one only on the job's own page — had no route to being scored at all unless you saved it through the browser extension. It is now fetched and scored like any other. Separately, a job whose posting date was unknown was skipped by the deeper scoring pass entirely, rather than being scored on what was known about it.
• Skills you added before choosing a career field now count toward your match scores. If you recorded your skills first and picked your field afterwards, those skills stopped being counted — every job showed a 0% match, with nothing to explain it. Skills now count whichever order you did things in. If this affected you, your scores are recalculated.
• "Scores updating…" stops when the scoring does. The feed could show that message indefinitely for an account with no résumé on file, while scoring had in fact finished. The feed now believes what the scoring reports rather than inferring from an empty column.

Reading a listing

• Words stop running together in job descriptions. Six job sources were removing HTML formatting from descriptions by deleting it, which welded the words on either side into one — "Location: LondonWorking Pattern: Hybrid". Formatting is now replaced with a space, and paragraph breaks are preserved. This affects listings as they arrive; listings already stored this way are repaired separately.

Settings that do what they say

• The career-field question no longer takes over the page you clicked. Clicking Applications, or Skills, or Settings, could land you on the career-field selection page instead. The question now appears once at sign-in, at most five times across separate sign-ins, and never in place of a page you asked for.
• "Skip for now" now means skip. Declining the career-field question was silently recording "General" as your answer — a field that feeds how your jobs are scored. Declining is now recorded as a decline, and nothing is chosen on your behalf.
• Turning off US Government jobs turns them off. The coverage switch for the US Government feed had stopped having any effect, so that source was searched for everyone regardless of the setting. The equivalent switch for remote-only sources was fixed in 3.11.0; this is the other half of it.

Under the hood

Thirty dependency updates across the platform, and several improvements to the checks that run before a release ships. Nothing you will notice, which is the intent.