A venv made with --symlinks is run and stored as itself, not as the base Python its python.exe links to: validate_interpreter returned the canonical path, so `--env .venv update --all --yes` would have changed the system Python. Canonicalizing now only decides where a link leads and whether it is PipDock's own; a link to another program is refused, and a Microsoft Store alias (os error 1920) is judged by its own path. The GUI merges and removes an added row by its path rather than by envHash, which follows links: a re-add replaces a broken row, removal sticks for an entry whose file is gone (a share), and neither runs during a scan. Added entries are validated again on every listing in both heads (envs::probe_listed), and the CLI checks its stored default when it uses it. `env remove` makes a typed path absolute first. SECURITY section 2 and env_probe's doc claimed an enforcement point over IPC; they now say what is checked, and backlog X36-b records the rest. notify.yml reports a Triage failure on a pull request. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
21 KiB
1.x
Newest first. See README.md for the conventions, and docs/ROADMAP.md for what each
slice cost and what it taught — that is a different document for a different reader.
1.6.0 — 2026-11-21
Add any Python, and the move to maintenance mode. PipDock can now manage a virtual environment wherever it lives — the one core feature that was still missing — and with this release it moves from being developed to being maintained. (#119, #120)
Added
- Add interpreter… on Environments — beside Rescan, in the empty screen, and in
Ctrl+K. Pick anypython.exe, typically the one in a virtual environment'sScriptsfolder, and it is added to the list, selected, and remembered across restarts. Until now the app only found a venv named.venv,venv,envor.envin the folder it was started from, which for an installed app is its own install folder — so most project environments were out of reach. - Remove from list on every interpreter you added. It only forgets the entry; nothing on disk is touched, and the environment's pins and snapshots are kept for when you add it again. An added environment that has since been deleted stays listed with its error, so you can remove it.
- The same from the command line:
pipdock env add <path>andpipdock env remove <path>, andpipdock env listshows what you added after what it discovered.
Changed
- PipDock checks a path you give it before running anything. An interpreter you pick, or pass
with
--env,env useorenv add, has to be a file namedpython.exe(orpython3.exe,python3.12.exe, the free-threadedpython3.14t.exe), and cannot be one of PipDock's own tool environments. Anything else is refused withPD-ENV-001, whose message now reads "That interpreter is missing, or PipDock cannot run it." An interpreter you added is checked again whenever the list is read, and a default set withenv usebefore 1.6.0 is checked when it is used — if it is refused, it is skipped with a warning, as a deleted one already was. - The repository moved to
github.com/poli0981org/pipdock. The bug-report button, the legal documents, About and the docs point there; the old address redirects. - The first-run screen asks once more. The privacy policy now names the interpreter paths you add (kept until you remove them) and the repository's new address, so the documents changed.
Verifying a download
gh attestation verify .\PipDock_1.6.0_x64-setup.exe --repo poli0981org/pipdock verifies this
release and later ones. The command in earlier READMEs no longer works for 1.4.0 and 1.5.0: an
attestation stays with the account that made it, so verify those with
--owner poli0981 --signer-repo poli0981/pipdock instead.
What maintenance mode means for you
- Bugs, UI/UX problems and accessibility barriers are what PipDock is now maintained for, along with dependency and security updates, major runtime upgrades and wording fixes. There is a new issue form for wrong or misleading text, in English or Vietnamese.
- New features are not taken. An issue or pull request asking for one is labelled and closed
automatically, with a link explaining why.
CONTRIBUTING.mdsays what is accepted.
1.5.0 — 2026-11-10
The accessibility release. PipDock could already be driven from the keyboard and read by Narrator from end to end — that was tested by hand on 1.4.0, and nothing blocked. This release fixes the places where it worked but made you work for it, and writes down honestly what is and is not supported. (#107)
If you use the keyboard
- Focus no longer disappears when the screen changes. Starting an update, a run reaching its
summary, opening a package's dependencies or opening an environment each replaced the screen and
left focus on nothing, so the next
Tabstarted again from the top of the window. Focus now lands on the new screen's heading. Closing the console drawer returns it to the button that opened the drawer. - Code Health's tabs are one tab stop, moved through with
←→HomeEnd. They were three. - A version conflict's three choices are one tab stop, moved through with the arrow keys.
Nothing is chosen until you press
SpaceorEnter— an arrow key will never open Force latest's confirmation. - The command palette scrolls with its selection. Past the ninth action the highlight used to leave the visible list.
- A button you have just pressed keeps focus while it works. Use, Rescan, Run, Run audit, Add, Download the index and Stop used to drop it the moment they went busy.
- The focus ring on a package row is complete. Three of its four sides were being cut off.
- The first-run screen puts focus on its heading rather than nowhere, and accepting it puts focus on the first screen.
If you use a screen reader
- Dialogs say what they are asking. A confirmation used to be announced by the package name alone — "numpy, dialog", then "Cancel". It is now named by its heading and described by its text.
- Search tells you what it is doing: that it is searching, how many results came back, and when nothing matched. Which result's details are showing is announced, not only coloured.
- Code Health's tabs are named for what you see —
deptry 3, followed by what the tool checks — so "click deptry" works with voice control too. - A pin's lock chip says what it means. A held pin used to read as a bare version number; the explanation was a mouse-only tooltip.
- The package table is a well-formed grid: every column has a header, the checkbox is in a cell, and the table says more than one row can be selected.
- The console drawer's close button is called Close console. It was called Cancel, next to a Stop button that cancels the run.
- Each sidebar tab exposes its
Ctrl+1…Ctrl+9shortcut.
If you use a Windows contrast theme
- Every destructive button is marked, with a double border. High contrast removes the red, and a button that removes, forces or rewrites was then drawn exactly like the Cancel beside it. A border was meant to mark them and, it turns out, had never actually been drawn.
- The current sidebar tab is outlined. It was indistinguishable from the rest.
For everyone
- The sidebar's shortcut hints (
^1…^9) are no longer drawn at half strength. - The link to vulture's whitelist is underlined all the time, not only under the mouse.
- The remove button in Search's install list is large enough to hit.
Added
- ACCESSIBILITY.md — what is supported, exactly what has been tested and by whom, what has not been tested, the known limitations, and how to report a barrier. The target is WCAG 2.2 AA; it is a target, not a claim of conformance.
- An Accessibility section in About, with a button that opens the statement and a new address,
accessibility@poli0981.dev, for anyone who would rather not use GitHub. - An accessibility issue form that asks what got in your way, not what caused it.
- CONTRIBUTING.md and a Code of Conduct, for anyone who wants to help.
Worth knowing
- There is no zoom yet. It was built for this release and held back, because at 200 % in the default window the package names disappeared. The Windows display scale works as before.
- Narrator has not been run again on this release. The changes above were checked in the running application against what it exposes to assistive technology, and by automated tests — not by listening. If something sounds wrong, that is exactly the report the new address is for.
- The legal documents did not change, so the first-run screen does not reappear.
- Also in this build since 1.4.0: pip 26.3's new wording for an unloadable build backend is recognised (it was reported under a neighbouring error code, with the same advice), and dependencies are current.
Verifying a download
As for 1.4.0: check the installer against SHA256SUMS.txt, or run
gh attestation verify <file> --repo poli0981/pipdock.
1.4.0 — 2026-10-17
No new feature: everything PipDock already did, made to do what it said. A review of the whole codebase found about 170 problems, and this release fixes every serious one. Several were in the part that matters most — checking a change before it happens — so if you skip release notes as a rule, read the first section.
Fixed — the safety checks
- A preview that is out of date is refused. A plan confirmed more than ten minutes after it was
made, or for an environment something else changed in the meantime, is refused before anything
is written (
PD-RES-002). This check existed and never ran. - A version your Python cannot run is never planned. PipDock now checks every release's
Requires-Pythonitself, for pip and for uv alike. A package that cannot be updated for that reason is listed under Left out — needs a different Python, with the range it needs and the Python you have, instead of pip's misleading "not found" — or uv quietly planning it anyway. - Force latest forces. It used to change nothing. It now installs the newest release, and the preview has a Will break section naming each package that will stop working and the requirement of its that is being overridden; the Confirm button counts them.
- Restoring a snapshot with the other engine no longer removes pip.
ruff --fixonly changes the files the report showed you. It used to fix everything it could reach, including files inside.venvand notebooks the report had excluded.- A failed build is a failure. With uv, a package whose build failed showed as "nothing to change".
- Stop, a timeout or a network outage mid-install now ends with a summary of what happened and the snapshot to restore from, instead of an internal error and nothing else.
- After a run, a check that could not run says so, instead of showing nothing — which read as everything being fine.
Fixed — everything else
- PipDock crashed on any environment inside a folder with accented characters in its name — every Vietnamese-named folder, for one. It no longer does.
- Interpreters installed under a path with a space in it are found.
- Requirements that only apply on another platform (
pexpect; sys_platform != "win32") are no longer reported as missing. - The PEP 668 setting now does what it says. It was a checkbox nothing read. Turning it on asks you first; while it is on, a red PEP 668 override chip shows on every screen where it applies, and only there.
- Decline on the first-run screen closes PipDock. It did nothing.
- The language you choose is kept after a restart.
- The window can be maximized and snapped, and opens at a size that fits your screen — on a laptop it used to open with the status line under the taskbar. The content stops widening at a readable width.
- Switching environment quickly no longer shows the previous one's data — package lists, update badges, snapshot diffs, the dependency view and pin suggestions could all land on the wrong environment.
- A run that failed to start could leave PipDock refusing every other change ("another change is in progress") until restart.
- Back while a preview is still being worked out now stops the engine, rather than leaving it running.
- The Security tab scrolls.
- Typing
/puts the cursor in Search from any screen — including Search itself, where it did nothing. Ctrl+1…Ctrl+9work on keyboard layouts where the digits need Shift, such as French.- F5, Ctrl+R, Ctrl+P and Ctrl+F no longer reload, print or search the app as if it were a web page.
- The package table's headings line up with their columns, and names stay visible at the smallest window size.
- Text on red badges is easier to read.
- A file PipDock cannot write — read-only, or open in another program — is reported as that, not as a full disk.
- Report bug includes your Python and engine versions, and still opens when the log is full of accented paths.
- Withdrawn ("yanked") releases in a plan are listed in the preview. They were detected and then never shown.
- Dialogs open in the middle of the window. They opened in its top-left corner.
- On a fresh install, Search offers to download the package index instead of saying it is "preparing" indefinitely.
Added
- PipDock keeps a log — one file a day in
%LOCALAPPDATA%\PipDock\data\logs\, kept for 14 days. Settings → Logs shows where, and copies the recent part for a bug report. The privacy policy has described this log since 1.0; now it exists. Nothing in it is sent anywhere. - If PipDock cannot open its data folder, it says so in a dialog, with the log's location, instead of not starting.
- Settings shows each engine's version for the selected environment, and not found when one is missing.
- The plan panel names the environment it is about to change.
Changed for scripts (pipdock CLI)
--jsonprints exactly one JSON document per command, on stdout. Prompts, warnings and progress go to stderr. Scripts that read several documents, or skipped a leading line, need updating —docs/CLI-SPEC.md§6 lists every command's document.pipdock env useis honoured. The environment is--envif given, then the oneenv usechose, then a.venvin the current folder. Before,env usewas saved and ignored.- Ctrl-C stops a run: the engine is stopped, what completed is printed with the snapshot to restore from, and the exit code is 130.
--verboseand--log-filework. On an internal error, the log's path is printed.pipdock updatewith no package and no--allis a usage error (exit 2) rather than a silent no-op.pipdock auditfollows--engine;pipdock doctorno longer requires pip when uv is the configured engine.
You will see this once
The first-run legal screen appears again. The privacy policy now describes the log and the tool environments PipDock keeps, and the third-party notices name osv.dev; PipDock also stopped computing the documents' version differently depending on how the files were checked out. Your acceptance is recorded against that version, so it asks once more. Nothing else resets.
Verifying a download
Each installer now carries a build attestation as well as its checksum:
gh attestation verify <installer> --repo poli0981/pipdock proves it was built by this
repository's release workflow from the tagged commit. SHA256SUMS.txt is also readable by
sha256sum -c on any system now.
1.3.0 — 2026-08-20
The dependency view — what depends on a package, what it depends on, and what a removal would cost.
Added
- Dependencies, from any package row: the
⇄button beside pin and remove. The package sits between two columns — everything that requires it and everything it requires — and every row carries the version specifier written on that edge, so you can see why something is held where it is rather than only that it is. Click any neighbour to move the view onto it. - The two numbers underneath: how many packages a removal would leave with a missing dependency, counted all the way through rather than one hop, and how many packages this one pulls in itself. This is the part the package list could never tell you.
- Requirements nothing satisfies. If something in the environment declares a dependency that is not installed, the view says so. Nothing else in PipDock reports this, and it only counts requirements that actually apply to your Python — a backport gated on 3.9 is not a hole.
- The environment's dependencies are read once when you open the view, so moving from package to package is instant.
Changed
- Package rows now have three buttons instead of two. Removing a package is still three clicks; the new one does not sit in front of it.
- There is no node-link diagram, and there was never going to be a useful one. Drawn as a picture, a real environment is unreadable: on a 352-package install the average package has 172 others within two steps, and more than 200 of them exceed 60. So the view shows one step at a time and lets you walk it, and answers the "everything downstream" question with a number instead. No new third-party code was added to the application for this.
1.2.0 — 2026-08-18
The Security tab, which the sidebar has shown greyed out since M2.
Added
- Security (
Ctrl+7) — known advisories against the packages installed in the selected environment, grouped by package. Each carries its id, the versions that fix it, its other ids (which is where the CVE is), the advisory text, and a link to its entry on osv.dev. - Cancel, because an audit takes 18–68 seconds — the first one longer, since it builds its own tool environment.
- Save report…, writing Markdown and JSON beside a path you choose, as Code Health already did.
pipdock auditat the command line. Exit 1 when it finds something, 0 when it does not, so a script can branch on it.- The Security tool environment is now listed in Settings → disk usage, and can be cleared there.
Changed
- There is no severity column, and there was never going to be one. The documentation promised findings sorted by severity; pip-audit publishes no severity at all. Findings are ordered by package, then by whether anything fixes them, then by id — the distinction that changes what you can do about one. PipDock does not invent a number to put in the gap.
- Advisories come from PyPI's advisory data. PipDock still connects to nothing but pypi.org; the osv.dev link is your browser going there after you click it.
You will see this once
The first-run legal screen appears again. The licence, disclaimer and third-party notices all described pip-audit as planned and not yet used, and that stopped being true. Your acceptance is recorded against the documents' version, so a change to them asks once more. Nothing else resets.
Fixed
- The update preview named the blocking package twice — "scipy requires scipy 1.11.4 requires numpy…". It now reads once, with the version.
- Clearing the cache reported a total that left out one of the two tool environments.
1.1.0 — 2026-08-14
Four smaller features, the day after 1.0.0.
Added
- Pin auto-suggest — packages that many others depend on are offered for pinning, on the Pins screen, with the count as the reason. The threshold is in Settings; zero turns it off.
- Export and import — write an environment as
requirements.txtorconstraints.txt, and read a requirements file back in as an install queue. Lines PipDock will not act on (includes, editable installs) are listed rather than silently dropped. - Disk usage in Settings — what PipDock has written, and a way to clear the parts that are safe
to clear.
index.dbis shown but not clearable: it holds your settings, pins and consent record as well as the package index. Ctrl+K— a command palette over every screen and action.
1.0.0 — 2026-08-14
First public release. Windows.
Bulk-manage packages across your Python environments, over pip or uv. Every change is previewed before it runs, the environment is snapshotted before it is touched, and a batch reports back package by package rather than stopping at the first failure.
- Environments discovered from the registry,
py -0p, uv-managed installs and the usual venv folder names, with a Browse… fallback still to come. - Installed / Updates — the whole environment, what is outdated, and a preview that explains what is holding a package back and which installed package declared the constraint. No engine reports that; PipDock derives it.
- Snapshots and rollback, including a rollback of a rollback.
- Pins, so a bulk update leaves what you have chosen to keep.
- An uninstall guard that refuses a removal other packages depend on, naming them and their constraints.
- Code Health — deptry, vulture and ruff over a project folder, from an isolated environment
PipDock builds for itself, with a gated
ruff --fix. - English and Vietnamese throughout the interface.
- A command line with the same behaviour, documented exit codes and
--json.
No telemetry, no account, no self-update. It connects to pypi.org and nowhere else.