aa813f0c89
PyPI renders the README alone; ./INSTALL.md, ./SPEC.md and ./CHANGELOG.md have nothing to resolve against. Links now point at the public Gitea repository (anchors kept). 0.13.0's page is immutable and keeps its broken links; the project page shows the newest release's README. Found by the owner on the 0.13.0 page. Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
13 KiB
13 KiB
Changelog
Notable changes are listed here. Release numbers match
pyproject.toml. Newest entries are first.
Format follows Keep a Changelog and Semantic Versioning.
[Unreleased]
- Nothing yet.
[0.13.1] - 2026-11-19
Fixed in 0.13.1
- The PyPI README's repo-relative links (
./INSTALL.md,./SPEC.md,./CHANGELOG.md) 404 on pypi.org - the package metadata holds only the README itself. They now point at the public Gitea repository (https://gitea.nolivaldeziii.com/nvaldez/daedalus/src/branch/main/...) with their anchors kept. 0.13.0's already-published page keeps its broken links (PyPI metadata is immutable); the project page shows the newest release's README. Found by the owner on the 0.13.0 page.
[0.13.0] - 2026-11-19
Changed in 0.13.0
- PyPI distribution renamed to
daedalus-tools(fromdaedalus): PyPI policy-blocks the plain name - the upload of 0.12.1 was rejected with "The name 'daedalus' isn't allowed" (near the existingdaedalus-cliandpydaedalusprojects). Thedaedaluscommand, thedaedalusimport package, the registry, and the repository are unchanged; only the value of[project] name(and hello's installed version lookup) moved.pipx install daedalus-toolsputs the samedaedalusCLI 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 todist/; 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 whenlatest(or any other tag) shared the release commit:git describe --tags --exact-matchreturns whichever name git picks, not the version tag. The guard now checks thatv<version>is amonggit 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 ofdaedalus publishon 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 taggedv<version>, the version not yet on PyPI (immutable once published), andbuild+twinepresent in the running interpreter — then runs the chainedpython -m build(the sdist must rebuild the wheel) andtwine check.--uploadhands exactly this version's sdist and wheel to twine; credentials stay with twine (~/.pypircor the prompt,__token__). Specpython/src/publish/spec.mdfirst, then tests, then code (SPEC 6.12).- Release tooling (
build,twine) added torequirements.txt.
Fixed in 0.12.0
- Release-blocking sdist defect: the sdist could not rebuild its
wheel (
package directory 'powershell' does not exist) — the emptypowershell//batch/folders were declared in packaging but never shipped, so installing from an sdist of 0.11.0 failed. Empty script folders now carry aREADME.mdplaceholder andMANIFEST.inships them (SPEC item 9.2.1). The chained build inpublishkeeps 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 viassh-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 theconfigure_sshhint. 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 theregister-python-argcompletethat 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~/.bashrcbetween managed markers (or--bashrc FILE), idempotently: an already-registered bashrc is left untouched.--dry-runprints the block and the target; on Windows the script prints a notice and does nothing; a zsh$SHELLgets a logged warning about thebashcompinitpreamble. Exit 3 when the register script is nowhere to be found. The full behavior ispython/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 ofinitialize_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-runprintsalready readyor the install command and changes nothing. Intended as the on-site companion tostore_publickey --fingerprinton a bare server. Spec section 12 written first, then tests, then code (SPEC 6.12);initialize_yubikeystep 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 ofsend_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'sauthorized_keys— so the machine holding the YubiKey can ssh in afterwards. Same five sources assend_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-keysoverride,--dry-run. Spec section 11 written first, then tests, then code (SPEC 6.12).- New shared source
--file PATHfor bothsend_pubkeyandstore_publickey: a file holding the SSH public key line, typicallyyubikey_auth.pubcarried 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-managedHost <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 unmanagedHostwith 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.mdin a Python script's folder,<name>.spec.mdbeside 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 withgpg --export-ssh-keyin 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'sauthorized_keys— idempotent (grep before append), perms enforced.--no-verifyskips the check explicitly;--dry-runresolves and prints without side effects. 22 new tests.
[0.5.0] - 2026-11-18
Added in 0.5.0
gpgtools(Python, categorygpg): YubiKey GPG/SSH helpers.daedalus gpgtools initialize_yubikeyruns 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 withgpg --fetch-keys, and writes the gpg-agent SSH config (enable-ssh-support, cache TTLs) with the GNUPGHOME directory at mode 700.--dry-runprints 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, defineshelp()(usage) andmain(), and ends withdaedalus_bash_dispatch "$@", which routeshelp/-h/--helptohelp()and everything else tomain()unchanged.- Bash script completion (SPEC item 3.13.5.2):
daedalus <name> <TAB>completes--help,-h, andhelpfor scripts implementing the interface; no script runs on TAB. Scripts without the interface get the shell default. bash/hello_bash.sh: sample bash script (categorytest) through the shared interface, the bash twin ofhello, with tests.bash/tests/: the interface tests — helper behavior through a sample script and enforcement of the interface for every registered.shscript.
[0.3.0] - 2026-11-18
Added in 0.3.0
- Shell completion via argcomplete
(new dependency):
daedalus hel<TAB>completeshello, category labels complete together with the scripts they filter (daedalus test h<TAB>), options complete after-, and--path <name>completes script names. Activate witheval "$(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 withargcomplete.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/--helpprints 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 (categorytest) 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(defaultgeneral),daedalus <category>listing (AND when several) anddaedalus <category>… <name>runs; script names and category labels never collide. - New listing format:
Daedalus Version:line,script/type/categoriestable, descriptions wrapped to the terminal width and indented, colors viaNO_COLOR/FORCE_COLOR. daedalus/run_python_script.py:.pyscripts run through a child entry that sets upsys.path, logging,sys.argv, and exit codes.daedalus.daedalus_logging: file logging to~/.daedalus/debug.logplus a colored stderr console handler (DAEDALUS_LOGLEVEL,DAEDALUS_NO_LOGGING).- Library imports: shared code imports as
daedalus.<folder>; the checkout registerspython/src/<folder>as packages on import and the child getsREPO_ROOTonPYTHONPATH. - Exact error messages for every usage failure, with close matches after a category prefix.
Changed in 0.1.0
SPEC.mdrewritten 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.