docs(changelog): 1.6.0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
e15d1637b0
commit
567142901f
1 file changed
+47
@@ -3,6 +3,53 @@
|
||||
Newest first. See [`README.md`](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](https://github.com/poli0981org/pipdock/pull/119),
|
||||
[#120](https://github.com/poli0981org/pipdock/pull/120))
|
||||
|
||||
### Added
|
||||
|
||||
- **Add interpreter…** on Environments — beside *Rescan*, in the empty screen, and in `Ctrl+K`.
|
||||
Pick any `python.exe`, typically the one in a virtual environment's `Scripts` folder, and it is
|
||||
added to the list, selected, and remembered across restarts. Until now the app only found a venv
|
||||
named `.venv`, `venv`, `env` or `.env` in 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>` and `pipdock env remove <path>`, and
|
||||
`pipdock env list` shows 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 use` or `env add`, has to be a file named `python.exe` (or `python3.exe`,
|
||||
`python3.12.exe`, the free-threaded `python3.14t.exe`), and cannot be one of PipDock's own tool
|
||||
environments. Anything else is refused
|
||||
with `PD-ENV-001`, whose message now reads "That interpreter is missing, or PipDock cannot run it."
|
||||
- **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.md` says what is accepted.
|
||||
|
||||
## 1.5.0 — 2026-11-10
|
||||
|
||||
**The accessibility release.** PipDock could already be driven from the keyboard and read by
|
||||
|
||||
Reference in new issue
Block a user