Skip to content

jobdork 0.15.2

Choose a tag to compare

@github-actions github-actions released this 27 Oct 10:35
· 459 commits to main since this release
Immutable release. Only release title and notes can be modified.
d6ec586

Download

For Download
Mac with Apple Silicon (M1 or later) jobdork-0.15.2-macos-arm64.dmg
Windows 10 or 11, 64-bit jobdork-0.15.2-windows-x64-setup.exe
Docker (a NAS or a server) docker pull jessengolab/jobdork:0.15.2
Checksums of the two installers SHA256SUMS.txt

Mac: open the .dmg and drag jobdork into Applications. Windows: run the setup; it installs for you alone, no administrator needed. Linux, an Intel Mac, or from source: the ways to run it. New to jobdork? The user guide shows every page of the app.

The first time you open it

The installers are not signed yet, so each system warns once:

  • macOS says it cannot check jobdork for malicious software. Click Done,
    open System Settings → Privacy & Security, scroll down to the line about
    jobdork and click Open Anyway, then Open Anyway again.
  • Windows shows "Windows protected your PC". Click More info, then Run anyway.

Verify Build Package

An installer: compare its SHA-256 with SHA256SUMS.txt, or with the GitHub CLI:

gh attestation verify jobdork-0.15.2-macos-arm64.dmg --repo jessn-dev/jobDork

The image jessengolab/jobdork:0.15.2 is exactly:

jessengolab/jobdork@sha256:7be67ef6a4d5a97c994cfa920f0aeaa576a21919a330b4e86173030b6f9bbb49

Built, scanned, checked and signed by this repository's workflow after approval.
Verify it before you run it, then pull it by that digest:

cosign verify jessengolab/jobdork@sha256:7be67ef6a4d5a97c994cfa920f0aeaa576a21919a330b4e86173030b6f9bbb49 \
  --certificate-identity-regexp '^https://github.com/jessn-dev/jobDork/\.github/workflows/docker\.yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

The installers are unsigned: how to open them. Privacy: PRIVACY.md.

What changed

7 changes in this release, newest first (click to read)

Changed — 2026-10-27 — version 0.15.2

0.15.2 carries the 6 entries below, everything since 0.15.1 (26 October).
The ones a user notices most:

  • Keys, your choice: asked for again after jobdork closes or updates, or
    kept in your computer's own keychain (macOS Keychain, Windows Credential
    Manager, Secret Service on Linux). Never in a file: the old plain
    source-keys.env is moved to the keychain or dropped at the first start,
    and deleted. Start over and removing jobdork always remove kept keys.
  • An update window that shows each step, from asking GitHub to opening
    the installer, then how to finish installing; a failure says why.
  • Remove jobdork from a computer, choosing what of yours goes: the
    Windows uninstaller asks, and Settings and jobdork uninstall do the same
    on a Mac or Linux.
  • Posts from every aggregator (Adzuna, Himalayas, Arbeitnow, Kalibrr) are
    checked against the employer's own board, and a post's window can ask that
    board now. Search Google Jobs sits above the list.
  • The README opens on a banner.

Updating from 0.15.1 with its own Update button uses 0.15.1's notice, not
the new window, which shows from the next update on. At the first start of
0.15.2, keys you entered before are gone from memory, as after any restart:
the new Enter your keys window asks for them, and asks where an old
source-keys.env's keys should go. On a Mac, keeping keys in the Keychain
means the Mac asks once after each update to let jobdork use it.

Changed — 2026-10-27 — Keys: asked for again after a restart, or kept in the computer's keychain by choice

After jobdork closed or updated, AI keys held in memory were gone and
nothing asked for them: the AI simply stopped, with a line on the Dashboard.
Adzuna and USAJOBS keys lived in a plain-text file, data/source-keys.env.

  • A choice on setup's first page and in Settings, Your keys: ask for keys
    each time jobdork starts (the default; memory only), or keep them in this
    computer's own encrypted store: the macOS Keychain, Windows Credential
    Manager, or the Secret Service on Linux (keyring, core/keystore.py),
    encrypted with your login. Turning it on keeps the keys entered so far;
    off removes the kept copies; Forget saved keys removes them all.
  • No key is written to a file any more, AI or job source. An old
    source-keys.env is read for one run while the page asks Keep them in
    the keychain or This time only; the file is deleted either way.
  • Enter your keys: when jobdork starts without a key its AI page or job
    sources use, a window asks for them (AI keys, and the Adzuna or USAJOBS
    keys you had given, which are tested before they are kept). Not now
    leaves it until the next start. jobdork remembers which job sources you
    gave keys for, by name only (key_sources).
  • A kept AI key comes back from the keychain after the idle wipe or a
    restart; Forget on the AI page removes the kept copy too.
  • Kept keys never outlive jobdork: Start over and removing jobdork
    (Settings, the Windows uninstaller, jobdork uninstall) always remove them
    from the keychain, with the scheduled scan; when removing, they are not one
    of the items to choose.
  • On a Mac, an unsigned app is asked "jobdork wants to use your
    keychain" once after each update (Always Allow); until then a scheduled
    scan runs without the kept keys. Said on both pages and in the guide.
    Containers have no keychain: the page says so, and keys come from the
    environment as before.
  • The desktop build carries keyring and its backends, and its self-test
    checks the Mac and Windows builds can reach the keychain. Docs: PRIVACY,
    CONFIG (remember_keys, key_sources), DECISIONS, run guides, README, and
    the guide's Settings, AI, Getting started and glossary pages.

Changed — 2026-10-27 — Search Google Jobs sits above the list

"Not here? Search Google Jobs for devops engineer, site reliability
engineer, …" was a small grey line after the last job post: seen only by
someone who scrolled to the end of a long list.

  • A bar above the list, under the count: "Not finding it here? Search
    Google Jobs:" and a button for each of your titles (the first six). With
    nothing matching it says "Nothing here." The same links as before: each
    opens Google's job results in your browser, for that title near you, or
    remote; jobdork sends Google nothing.
  • Guide: Job posts, and its picture.

Changed — 2026-10-27 — Posts from every aggregator are checked against the employer's own board, and the window can ask it now

The flag for a post missing from the employer's own board covered Adzuna
alone, and could almost never fire: of 604 Adzuna posts in one person's
jobs, 2 could be checked. jobdork counted a board as read only when one of
its jobs was stored, so a board that answered with nothing matching (the
very case of a job it does not list) left no trace.

  • Every aggregator: Adzuna, Himalayas, Arbeitnow and Kalibrr, which
    carry many employers' jobs. Not USAJOBS (federal agencies' own listings)
    nor Workable's search (each post is from the employer's own Workable).
  • Each scan records the employer boards it read (board_reads, schema
    13): the employer, the board, when, and whether to the end. No job data.
    A board read to the end vouches even when nothing on it matched.
  • Only a whole read vouches. Workday, SmartRecruiters, Eightfold, Oracle
    and Taleo stop at a page limit, and careers sites read the newest few; a
    board cut short, failed, or answering empty (possibly throttled) is not
    read to the end, and a missing job there says nothing.
  • The job post's window says what the board said (on it, not on it,
    read only partly, not read) and has Check the employer's own board:
    it searches that board for the post's own title now and says whether it
    is there, with a link, or why it cannot tell. For a board the scan read
    only partly or not at all, or to look again before applying.
  • Guide: Tags and the job post's window.

Changed — 2026-10-27 — The README opens on a banner

The README's title was the small icon beside "jobDork" in heading type. It
opens now on a banner, as Guardrails AI's does: the icon, the name large,
and "Find the job posts worth your time" beneath, 560 pixels wide, then a
rule and the badges.

  • docs/images/banner-light.svg and banner-dark.svg, drawn from
    packaging/icon.svg; GitHub shows the dark one on a dark page.
  • Cropped to the artwork, so it sits centred; each line's width is fixed,
    so Windows' wider font cannot run it off the edge.

Added — 2026-10-27 — Remove jobdork from a computer, choosing what of yours goes

Windows' uninstaller removed the program and left everything else,
including the scheduled scan's task, which went on starting a program that
was gone. On a Mac or Linux there was no uninstall at all: dragging the app
to the Trash left the scheduled scan and every file behind.

  • One way to remove it everywhere (core/uninstall.py). The scheduled
    scan and the app window's storage always go. Of the person's, each item is
    its own choice and none is chosen: settings, job posts (with their
    backups), the resume, letters and tailored resumes, saved job-source keys,
    logs, and installers Update left in Downloads. Only jobdork's folder, its
    documents folder and its own installers are ever touched; a link pointing
    elsewhere is not followed.
  • Windows: the uninstaller (Settings, Apps) shows the same items as
    tick-boxes before it removes the program; a silent uninstall keeps
    everything.
  • Settings, "Remove jobdork from this computer" in the desktop app on a
    Mac or Linux: tick, confirm, and it says what is left to do (Mac: quit and
    drag the app to the Trash).
  • jobdork uninstall from a terminal asks about each item, or
    --remove jobs,logs (or all).

Added — 2026-10-27 — An update window that shows each step

Updating from 0.15.0 to 0.15.1, Update showed a notice, "Downloading the
update. The installer opens when it has been checked.", and nothing after
it: the job had failed three times on its first request ("could not ask
GitHub for the release (URLError)"), and that was written only to the
activity list. Nothing said it had stopped, or that it was still going.

  • Update opens a window that follows the job: asking GitHub for the
    release, downloading the installer with a bar and how much is done ("44% ·
    52 of 118 MB"), checking it against the release's checksums, checking its
    build attestation, opening it. Each step is ticked off as it passes.
  • Then how to finish. Mac: Quit jobdork, drag jobdork onto
    Applications in the Finder window that opened and choose Replace, open it
    again. Windows: follow the installer, which closes jobdork and offers to
    open the new version.
  • A failure is shown in the window, with its reason and Release page
    to download it by hand. A download that drops part way now says so ("the
    download stopped (could not reach GitHub; is this computer online?)")
    rather than a Python error.
  • The app can quit itself when asked (quit_app, the page's one new call to
    the app); the guide's Settings page describes the window.