Release 1.0.0 - 2026-07-30 · jchultarsky/mirador

Release Notes

1.0 is a promise, not a feature. Nothing is added here that was not in
0.19.0. What changes is what the version number commits to:

Your config keeps working. No option that has ever shipped has been
removed. Re-verified before tagging against all thirty-one release tags —
1860 key comparisons, nothing lost. The four keys predating 0.1.0 are still
handled by mirador --migrate-config.
Your data files keep working. todos.toml, your notes, watchlist.toml,
zones.toml and state.toml have not changed shape since 0.1.0, and all
ignore keys they do not recognise — so a file written by a newer mirador still
opens in an older one.
No known crashes or hangs. Every module has been read adversarially, the
untrusted-input boundary is bounded on every side, and the dashboard has been
soaked across real midnights on macOS, Linux and Windows.

Breaking changes from here get a major version. Options may be added; they will
not be renamed out from under you.

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/jchultarsky/mirador/releases/download/v1.0.0/mirador-installer.sh | sh

powershell -ExecutionPolicy Bypass -c "irm https://github.com/jchultarsky/mirador/releases/download/v1.0.0/mirador-installer.ps1 | iex"

File	Platform	Checksum
mirador-aarch64-apple-darwin.tar.gz	Apple Silicon macOS	checksum
mirador-x86_64-apple-darwin.tar.gz	Intel macOS	checksum
mirador-x86_64-pc-windows-msvc.zip	x64 Windows	checksum
mirador-x86_64-unknown-linux-gnu.tar.gz	x64 Linux	checksum

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo jchultarsky/mirador

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>