Repository navigation
jobdork 0.15.3
Download
| For | Download |
|---|---|
| Mac with Apple Silicon (M1 or later) | jobdork-0.15.3-macos-arm64.dmg |
| Mac with an Intel processor | jobdork-0.15.3-macos-x86_64.dmg |
| Windows 10 or 11, 64-bit | jobdork-0.15.3-windows-x64-setup.exe |
| Docker (a NAS or a server) | docker pull jessengolab/jobdork:0.15.3 |
| Checksums of the installers | SHA256SUMS.txt |
Mac: open the .dmg and drag jobdork into Applications. Windows: run the setup; it installs for you alone, no administrator needed. Not sure which Mac you have? Apple menu → About This Mac: "Chip" is Apple Silicon, "Processor … Intel" is Intel. Linux, 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.3-macos-arm64.dmg --repo jessn-dev/jobDorkThe image jessengolab/jobdork:0.15.3 is exactly:
jessengolab/jobdork@sha256:b237047d60aef96b6254ac0b7260965a67e3760abb98117801059954aff8a03e
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:b237047d60aef96b6254ac0b7260965a67e3760abb98117801059954aff8a03e \
--certificate-identity-regexp '^https://github.com/jessn-dev/jobDork/\.github/workflows/docker\.yml@' \
--certificate-oidc-issuer https://token.actions.githubusercontent.comThe installers are unsigned: how to open them. Privacy: PRIVACY.md.
What changed
4 changes in this release, newest first (click to read)
Changed — 2026-10-27 — version 0.15.3
0.15.3 carries the 3 entries below, everything since 0.15.2 (27 October):
- A desktop app for Intel Macs,
jobdork-0.15.3-macos-x86_64.dmg,
beside the Apple Silicon one: download, open, drag into Applications. - Install on a Mac with one command in Terminal, which checks the
download itself and skips the first-open warning; and a WinGet manifest
written for every release and installed for real on every pull request. - What 1.0 promises, written down in docs/DECISIONS.md.
Updating from 0.15.2 uses the update window 0.15.2 brought. An Intel Mac
has no earlier jobdork to update: it starts at 0.15.3.
Added — 2026-10-27 — A desktop app for Intel Macs
The desktop app was built for Apple Silicon Macs only; on an Intel Mac the
only ways in were Docker or running from source, too much for someone who
just wants to download and install. From 0.15.3 every release has
jobdork-X.Y.Z-macos-x86_64.dmg beside the Apple Silicon one, built and
self-tested on GitHub's Intel Mac machines (macos-15-intel) and attested
the same way. macOS 12 or newer.
- The app's Update button takes the installer for the Mac it runs on,
and the one-command install for Macs does too. - The release page lists it, with how to tell which Mac you have (Apple
menu → About This Mac). - One library is older on the Intel app:
cryptography48.0.1, the
last version built for Intel Macs; every other build has 50.0.2. Three
advisories are fixed after 48.0.1: in PKCS#7 decryption (not used), in
slow certificate-chain building (the update check builds chains only from
Sigstore's own verified trusted root), and in DNS-name constraints (the
update check's certificates name a workflow, not a host). CI's dependency
audit accepts those three for that entry alone, audited separately from
the rest, which still allows none; the reasons are beside it in
.github/workflows/docker.yml. - Docs: the desktop guide, run guides, README, SECURITY.md, DECISIONS, and
the user guide's home page and Getting started.
Added — 2026-10-27 — Install on a Mac with one command, and a WinGet manifest for Windows
- One command installs or updates jobdork on a Mac
(packaging/install-mac.sh), pasted into Terminal:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/jessn-dev/jobDork/main/packaging/install-mac.sh)".
It asks GitHub for the newest release, takes the.dmgonly if GitHub
Actions uploaded it, checks its SHA-256 against the release's
SHA256SUMS.txtand, when the GitHub CLI is signed in, its build
attestation; then it quits an open jobdork, puts the new app in
/Applications (~/Applications when that cannot be written), keeping the
old one until the new one is in place, and opens it. No password, no
setting changed; macOS does not show the first-open warning, which is for
files a browser downloaded. Tested with stand-ins for the network and the
disk image (tests/test_install_mac.py): it installs, refuses a file that
does not match its checksum and keeps the old app, and refuses a file
GitHub Actions did not upload before downloading it. scripts/winget_manifest.py X.Y.Zwrites the WinGet manifest for a
release (three files in the 1.12 schema, in winget-pkgs' folder layout):
the Windows installer's address and SHA-256 from the release,innoand
per-user, so WinGet runs it silently, and the name Windows lists it under.
It is what a pull request to microsoft/winget-pkgs adds so that
winget install jessn-dev.jobdorkworks; that submission is planned
before 1.0.0.- Every release writes its WinGet manifest: the release workflow's last
step runs the script on the release's own checksums and keeps the three
files with the run (winget-manifest-vX.Y.Z, 90 days), after the release
page, so a manifest problem never holds up a release. - The manifest is tried for real on every pull request: a
wingetjob
on Windows writes one for the installer just built, serves the installer
from the runner, runswinget validate,winget install --manifest
(silent, as WinGet's own checks install a submission), checks the name,
version and publisher Windows lists it under and thatjobdork.exeis
there, thenwinget uninstalland checks both are gone. winget marks
what it downloads as from the internet, and Windows holds an unsigned
installer with that mark at a security prompt before it starts (tried:
without the mark it installs silently in a second; with it, it never
starts on a runner where nobody can answer). So on the runner.exe
files count as low risk; on a person's computer, installing with winget
shows Windows' prompt for an unsigned installer, as a browser download
does. - The Windows installer names the app "jobdork" under Installed apps
(UninstallDisplayName), instead of Inno Setup's "jobdork version
0.15.2": WinGet matches an installed app to its package by that name. - Docs: the desktop guide, the user guide's Getting started and home page,
and the README.
Added — 2026-10-27 — What 1.0 promises, and when it comes
docs/DECISIONS.md now says what a version number promises from 1.0.0 on:
patches fix, minor versions add, and only a major version may break your
settings file, your data, kept keys, the commands, the environment
variables, the installers and Docker image, or what PRIVACY.md rules out,
said in the notes with how to move over. The pages' look, scores, sources
and the database's tables are not promised. 1.0.0 is the public launch,
after 0.15.2's Update is checked, the security review's work, a few people
who do not program have installed it, and jobdork is in WinGet.