Skip to content

v1.7.1

Latest

Choose a tag to compare

@github-actions github-actions released this 11 Oct 14:46
· 0 commits to main since this release
32d9dce

New commands

  • inspect dotfiles: inventory .paredit metadata without reading file bodies.
  • inspect test-risk: rank named top-level Common Lisp and Emacs Lisp functions without naming-convention test links by complexity. This is static analysis, not execution coverage.
  • refactor bulk: apply wrap and syntactic rename-in-form operations with non-overlapping replacement spans against an original source snapshot, with validated preview and write modes. Rename does not resolve bindings.
  • refactor unwrap-body: remove a wrapper while retaining arguments from --body-start to the end. Multiple forms require a top-level or recognized sequence position. This is structural editing, not a guarantee of preserved semantics.

Fixes

  • Extend selected control-flow lint rules to Emacs Lisp cl-lib, respecting case-sensitive symbol identities.
  • Support printed Emacs Lisp reader objects as opaque data, preserving their payloads during formatting.
  • Add extract-local-function guards against assignments to free-variable cells.
  • Add multi-path edit kill with overlap rejection, and preflight kill-ring reads.
  • Validate all selected rewrites before the first write in ordinary lint fixes and refactor steps. Batch rollback is not universally guaranteed.
  • Make the package-chain complexity regression control deterministic by counting actual scan work. Existing positive CPU-time bounds remain enforced; the quadratic control must fail both work-growth bounds.
  • Measure the Clojure lint cost budget using thread CPU time on Linux and macOS, excluding scheduler waits. Preserve its generated inputs and 6× threshold; this finite-input budget is not proof of linear complexity.

Compatibility

  • Rust MSRV remains 1.85.
  • Incomplete inspect dotfiles inventories print their report and exit 3, without an enabling flag.
  • Capabilities metadata describes unconditional gates and classifies --intended-bump as a severity gate.
  • Capabilities schema IDs remain unchanged as optional fields are added. Obtain schemas from the same release or binary that produced the document: older cached strict schemas may reject new fields even when schema_version matches.