bd1a10487c
PyPI policy-blocks the plain name: the 0.12.1 upload was rejected with "The name 'daedalus' isn't allowed" (near the existing daedalus-cli and pydaedalus projects). The distribution is now daedalus-tools; command, imports, registry, and the repository name stay daedalus. hello's installed-version lookup follows. publish now derives artifact file names from the PEP 625 normalized name (daedalus_tools-<version>.tar.gz) - with a hyphenated project name the previously constructed names would have missed what setuptools writes to dist/ (publish spec 3.2, new regression test). Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
284 lines
12 KiB
Markdown
284 lines
12 KiB
Markdown
# Changelog
|
|
|
|
Notable changes are listed here. Release numbers match
|
|
[`pyproject.toml`](./pyproject.toml). Newest entries are first.
|
|
|
|
Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and
|
|
[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
|
|
## [Unreleased]
|
|
|
|
- Nothing yet.
|
|
|
|
## [0.13.0] - 2026-11-19
|
|
|
|
### Changed in 0.13.0
|
|
|
|
- PyPI distribution renamed to **`daedalus-tools`** (from `daedalus`):
|
|
PyPI policy-blocks the plain name - the upload of 0.12.1 was rejected
|
|
with "The name 'daedalus' isn't allowed" (near the existing
|
|
`daedalus-cli` and `pydaedalus` projects). The `daedalus` command, the
|
|
`daedalus` import package, the registry, and the repository are
|
|
unchanged; only the value of `[project] name` (and hello's installed
|
|
version lookup) moved. `pipx install daedalus-tools` puts the same
|
|
`daedalus` CLI on PATH (SPEC item 9.1).
|
|
|
|
### Fixed in 0.13.0
|
|
|
|
- `publish`'s artifact names now use the PEP 625 normalized name
|
|
(`daedalus-tools` -> `daedalus_tools-0.13.0.tar.gz`), matching what
|
|
setuptools actually writes to `dist/`; with a hyphenated project name
|
|
the constructed names would have missed the files. PyPI's version
|
|
probe keeps using the project name as written (publish spec 3.2).
|
|
|
|
## [0.12.1] - 2026-11-19
|
|
|
|
### Fixed in 0.12.1
|
|
|
|
- `publish`'s tag guard rejected a correctly tagged release when
|
|
`latest` (or any other tag) shared the release commit: `git describe
|
|
--tags --exact-match` returns whichever name git picks, not the
|
|
version tag. The guard now checks that `v<version>` is among
|
|
`git tag --points-at HEAD` (membership check, publish spec item
|
|
3.3.2); moving tags on the same commit are fine. Found by the first
|
|
live run of `daedalus publish` on the v0.12.0 release.
|
|
|
|
## [0.12.0] - 2026-11-19
|
|
|
|
### Added in 0.12.0
|
|
|
|
- `daedalus publish`: a guarded one-command PyPI release. Checks the
|
|
working tree is clean, HEAD exactly tagged `v<version>`, the version
|
|
not yet on PyPI (immutable once published), and `build` + `twine`
|
|
present in the running interpreter — then runs the **chained**
|
|
`python -m build` (the sdist must rebuild the wheel) and
|
|
`twine check`. `--upload` hands exactly this version's sdist and
|
|
wheel to twine; credentials stay with twine (`~/.pypirc` or the
|
|
prompt, `__token__`). Spec `python/src/publish/spec.md` first, then
|
|
tests, then code (SPEC 6.12).
|
|
- Release tooling (`build`, `twine`) added to `requirements.txt`.
|
|
|
|
### Fixed in 0.12.0
|
|
|
|
- **Release-blocking sdist defect:** the sdist could not rebuild its
|
|
wheel (`package directory 'powershell' does not exist`) — the empty
|
|
`powershell/`/`batch/` folders were declared in packaging but never
|
|
shipped, so installing from an sdist of 0.11.0 failed. Empty script
|
|
folders now carry a `README.md` placeholder and `MANIFEST.in` ships
|
|
them (SPEC item 9.2.1). The chained build in `publish` keeps this
|
|
from recurring.
|
|
|
|
## [0.11.0] - 2026-11-19
|
|
|
|
### Added in 0.11.0
|
|
|
|
- `gpgtools ssh-config-summary`: a read-only view of the gpg-enabled ssh
|
|
logins. One row per marker-managed block in `~/.ssh/config` (or
|
|
`--config FILE`): alias, hostname, user, the key id - first 8 chars of the
|
|
identity's SHA256 fingerprint via `ssh-keygen -lf`, with the SHA-256
|
|
material digest as fallback when ssh-keygen is unavailable - and the
|
|
fallback identity's name. No managed blocks (or a missing config) prints
|
|
that fact with the `configure_ssh` hint. Exit code always 0. Spec item 2.8
|
|
and section 13 written first, then tests, then code (SPEC 6.12).
|
|
|
|
## [0.10.0] - 2026-11-19
|
|
|
|
### Added in 0.10.0
|
|
|
|
- `daedalus init`: the one-time shell-side setup for tab completion.
|
|
Finds the `register-python-argcomplete` that belongs to this exact
|
|
daedalus interpreter (the pipx venv, the checkout .venv, or the
|
|
system python — argcomplete's script sits beside it), then appends
|
|
the completion hook to `~/.bashrc` between managed markers (or
|
|
`--bashrc FILE`), idempotently: an already-registered bashrc is left
|
|
untouched. `--dry-run` prints the block and the target; on Windows
|
|
the script prints a notice and does nothing; a zsh `$SHELL` gets a
|
|
logged warning about the `bashcompinit` preamble. Exit 3 when the
|
|
register script is nowhere to be found. The full behavior is
|
|
`python/src/init/spec.md` (sections 1-7), written first, then tests,
|
|
then code (SPEC 6.12).
|
|
|
|
## [0.9.0] - 2026-11-19
|
|
|
|
### Added in 0.9.0
|
|
|
|
- `gpgtools initialize`: checks that gnupg is ready on this machine
|
|
(`gpg --version`) and installs what is missing — the gnupg-only
|
|
half of `initialize_yubikey`, with no card expectations. Missing gpg
|
|
triggers the same manager detection and sudo install; the check
|
|
re-runs once after a successful install. `--dry-run` prints
|
|
`already ready` or the install command and changes nothing. Intended
|
|
as the on-site companion to `store_publickey --fingerprint` on a
|
|
bare server. Spec section 12 written first, then tests, then code
|
|
(SPEC 6.12); `initialize_yubikey` step 1 now runs the same shared
|
|
flow instead of its own inline copy.
|
|
|
|
## [0.8.0] - 2026-11-19
|
|
|
|
### Added in 0.8.0
|
|
|
|
- `gpgtools store_publickey`: the on-site bootstrap mirror of
|
|
`send_pubkey`. Run on the machine that access is being granted
|
|
**to** (a server with ssh password authentication disabled, no key
|
|
there yet, you at its console), it resolves one SSH public key and
|
|
appends it to this machine's `authorized_keys` — so the machine
|
|
holding the YubiKey can ssh in afterwards. Same five sources as
|
|
`send_pubkey`; by design there is no proof-of-possession (the
|
|
private half is elsewhere). Existing entries preserved verbatim,
|
|
idempotent by key material, `~/.ssh`/file modes forced to 700/600,
|
|
`--authorized-keys` override, `--dry-run`. Spec section 11 written
|
|
first, then tests, then code (SPEC 6.12).
|
|
- New shared source `--file PATH` for both `send_pubkey` and
|
|
`store_publickey`: a file holding the SSH public key line,
|
|
typically `yubikey_auth.pub` carried on a USB stick — no network,
|
|
no gpg needed. Several keys in one file refuse rather than guess.
|
|
- Both resolve-and-store subcommands now print an identity block (key
|
|
line, source, and the key material's SHA-256 digest) before acting,
|
|
so what was resolved can be compared across machines.
|
|
|
|
## [0.7.0] - 2026-11-19
|
|
|
|
### Added in 0.7.0
|
|
|
|
- `gpgtools configure_ssh` (guide step 7): writes a marker-managed
|
|
`Host <alias>` block into the ssh client config — YubiKey identity
|
|
first, fallback identity only when it exists, `IdentitiesOnly yes`.
|
|
Idempotent (re-runs replace the block; everything outside the
|
|
markers is preserved), `--dry-run`, and a guard that refuses when an
|
|
unmanaged `Host` with the same alias would shadow the block. Spec
|
|
items 2.5 and 10 written first, then tests, then code (SPEC 6.12).
|
|
- Per-script local specs (SPEC items 6.11, 6.12): every script gets a
|
|
spec that completely describes it — `spec.md` in a Python script's
|
|
folder, `<name>.spec.md` beside bash/PowerShell/batch scripts — in
|
|
the sectionized format of SPEC.md. Script work is spec first, then
|
|
tests, then code. First specs added:
|
|
`gpgtools`, `hello`, `hello_bash`.
|
|
|
|
### Fixed in 0.7.0
|
|
|
|
- Test fixtures no longer carry private values: the real server IP,
|
|
host alias, card serial, and public key fingerprint were replaced
|
|
with documentation-range placeholders.
|
|
|
|
## [0.6.0] - 2026-11-18
|
|
|
|
### Added in 0.6.0
|
|
|
|
- `gpgtools send_pubkey` (guide steps 5-6): resolves an SSH public key
|
|
from one of four sources — `--yubikey` (gpg-agent ssh socket),
|
|
`--url` (armored OpenPGP key, converted with `gpg --export-ssh-key`
|
|
in a throwaway GNUPGHOME), `--fingerprint` (store chain: local
|
|
keyring, keys.openpgp.org VKS, keyserver.ubuntu.com, each
|
|
fingerprint-checked), or `--pubkey` (literal line, format-validated).
|
|
Before anything is stored, proof of possession: a random challenge is
|
|
signed by the private half through the agent (`ssh-keygen -Y sign
|
|
-U`; PIN prompts reach the user) and verified against the candidate
|
|
line (`ssh-keygen -Y verify`). Only then is the line appended to the
|
|
target's `authorized_keys` — idempotent (grep before append), perms
|
|
enforced. `--no-verify` skips the check explicitly; `--dry-run`
|
|
resolves and prints without side effects. 22 new tests.
|
|
|
|
## [0.5.0] - 2026-11-18
|
|
|
|
### Added in 0.5.0
|
|
|
|
- `gpgtools` (Python, category `gpg`): YubiKey GPG/SSH helpers.
|
|
`daedalus gpgtools initialize_yubikey` runs the fresh-machine flow
|
|
(steps 1-4 of the wiki guide): installs gnupg when missing (apt-get,
|
|
dnf, pacman), checks the card, fetches the public key from the card's
|
|
URL field with `gpg --fetch-keys`, and writes the gpg-agent SSH
|
|
config (`enable-ssh-support`, cache TTLs) with the GNUPGHOME
|
|
directory at mode 700. `--dry-run` prints the plan; steps 5-7
|
|
(derive and deploy the SSH key per host) are server-specific and
|
|
intentionally out of scope.
|
|
|
|
## [0.4.0] - 2026-11-18
|
|
|
|
### Added in 0.4.0
|
|
|
|
- `bash/daedalus_common.sh`: the shared interface for bash scripts (SPEC
|
|
item 6.10) — a script sources its sibling helper, defines `help()`
|
|
(usage) and `main()`, and ends with `daedalus_bash_dispatch "$@"`,
|
|
which routes `help` / `-h` / `--help` to `help()` and everything else
|
|
to `main()` unchanged.
|
|
- Bash script completion (SPEC item 3.13.5.2): `daedalus <name> <TAB>`
|
|
completes `--help`, `-h`, and `help` for scripts implementing the
|
|
interface; no script runs on TAB. Scripts without the interface get
|
|
the shell default.
|
|
- `bash/hello_bash.sh`: sample bash script (category `test`) through the
|
|
shared interface, the bash twin of `hello`, with tests.
|
|
- `bash/tests/`: the interface tests — helper behavior through a
|
|
sample script and enforcement of the interface for every registered
|
|
`.sh` script.
|
|
|
|
## [0.3.0] - 2026-11-18
|
|
|
|
### Added in 0.3.0
|
|
|
|
- Shell completion via [argcomplete](https://github.com/kislyuk/argcomplete)
|
|
(new dependency): `daedalus hel<TAB>` completes `hello`, category
|
|
labels complete together with the scripts they filter (`daedalus test
|
|
h<TAB>`), options complete after `-`, and `--path <name>` completes
|
|
script names. Activate with
|
|
`eval "$(register-python-argcomplete daedalus)"` (INSTALL.md).
|
|
- Script arguments complete from the script's own parser (SPEC item
|
|
3.13.5.1): once the script name is typed, daedalus delegates the rest
|
|
of the line to the script — `daedalus hello -<TAB>` offers hello's
|
|
`-h` / `--help`, never daedalus's options. A Python script opts in
|
|
with `argcomplete.autocomplete(parser)` (SPEC item 6.9).
|
|
- `daedalus/completions.py`: the candidate functions argcomplete calls.
|
|
|
|
### Changed in 0.3.0
|
|
|
|
- The CLI argument handling now uses `argparse`
|
|
(`daedalus.cli.build_parser`): `-h/--help` prints the argparse
|
|
rendering, and parser-level errors keep the argparse messages (exit
|
|
code 2 stays). Options are parsed anywhere before the script words;
|
|
everything after the script name still goes to the script (SPEC item
|
|
3.1 unchanged).
|
|
- SPEC item 1.5 policy: reuse a popular, tested, trusted third-party
|
|
package when it exists instead of writing our own; argcomplete is
|
|
the first such dependency (SPEC item 9.6).
|
|
|
|
## [0.2.0] - 2026-11-18
|
|
|
|
### Added in 0.2.0
|
|
|
|
- `hello`: sample Python script (category `test`) that prints a hello
|
|
line and the daedalus version; first registered script, with tests and
|
|
an installed package entry (`daedalus.hello`).
|
|
|
|
## [0.1.0] - 2026-11-18
|
|
|
|
### Added in 0.1.0
|
|
|
|
- Categories: `Script.categories` (default `general`),
|
|
`daedalus <category>` listing (AND when several) and
|
|
`daedalus <category>… <name>` runs; script names and category labels
|
|
never collide.
|
|
- New listing format: `Daedalus Version:` line, `script` / `type` /
|
|
`categories` table, descriptions wrapped to the terminal width and
|
|
indented, colors via `NO_COLOR` / `FORCE_COLOR`.
|
|
- `daedalus/run_python_script.py`: `.py` scripts run through a child
|
|
entry that sets up `sys.path`, logging, `sys.argv`, and exit codes.
|
|
- `daedalus.daedalus_logging`: file logging to `~/.daedalus/debug.log`
|
|
plus a colored stderr console handler (`DAEDALUS_LOGLEVEL`,
|
|
`DAEDALUS_NO_LOGGING`).
|
|
- Library imports: shared code imports as `daedalus.<folder>`; the
|
|
checkout registers `python/src/<folder>` as packages on import and the
|
|
child gets `REPO_ROOT` on `PYTHONPATH`.
|
|
- Exact error messages for every usage failure, with close matches after
|
|
a category prefix.
|
|
|
|
### Changed in 0.1.0
|
|
|
|
- `SPEC.md` rewritten with stable item numbers (`SPEC item 3.7.1`), in
|
|
lockstep with the upstream scriptman specification.
|
|
|
|
## [0.0.0] - 2026-11-11
|
|
|
|
### Added in 0.0.0
|
|
|
|
- Empty template: CLI, CI, packaging, and script-integration guide with no
|
|
registered scripts.
|