GitoxideLabs/gitoxide gix-testtools-v0.21.0

gix-testtools v0.21.0

on GitHub

Chore

• make docs-rs work, and publishing

New Features

• redact unstable values in diagnostic snapshots

  Complete error snapshots expose useful context and causes, but temporary
  paths, dynamically assigned ports, object IDs, and platform-specific I/O
  messages make their output unstable.

  Add redact_debug_snapshot() to apply explicit replacements, reuse object-ID
  normalization, and render OS errors by their portable ErrorKind. Handle
  plain and debug-escaped Windows paths while retaining meaningful suffixes
  and unrelated backslashes. Return an owned Debug value so insta displays
  the diagnostic without additional quoting or newline escaping.

  Cover redaction, object identity, and OS error formatting, and convert the
  environment, SBOM argument, and Rust fixture error assertions to complete
  inline snapshots. The helper is available before downstream diagnostic
  snapshot migrations need it.

Bug Fixes

• Keep rust workspace tests inside disposable repositories and isolated environments

  Direct Git launches inherited repository selectors and user configuration even
  when tests supplied a fixture working directory. Tests of default-environment
  APIs and local Git transports also shared the runner's environment. A few
  journey tests wrote beneath source directories or used the source checkout as
  the repository under test.

  Use the shared gix-testtools Git command builder for subprocess setup, isolated
  repository options for fixtures, and isolated child processes where the real
  environment-reading API must be exercised. Scope CWD changes, copy the fixture
  used by an object-write test, and run shell journeys through jtt run. Keep
  journey worktrees and example output within their disposable sandboxes and
  replace the attributes checkout test with a representative fixture repository.
  Prompt examples also run in isolated children and must build successfully; the
  old tests could ignore build failures and execute stale cached binaries.

  The affected Rust crate suites, internal test-tool build, and max-pure journey
  suite pass from a source copy without Git metadata. Signing and Git-daemon
  checks use only disposable keys, repositories, and local sockets.

• isolate fixtures from inherited Git templates

  Fixture commands already ignore external Git configuration, but inherited
  GIT_TEMPLATE_DIR could still inject personal template files into repositories
  created by git init, making fixtures depend on the caller's environment.

  Clear that variable in the shared command setup used by fixture scripts and
  isolated Git helpers. Keep Git's installed templates available because existing
  fixtures rely on their standard files and directory layout.

  Document the isolation behavior and add a regression that supplies an external
  template containing a marker file, then verifies that git init does not copy
  it into the fixture repository.

• keep fixture scripts isolated when they set GIT_CONFIG_COUNT themselves
  The isolation configuration (no signing, no auto-maintenance, init.defaultBranch=main)
  reached scripts only as GIT_CONFIG_COUNT variables, so a script exporting its own
  GIT_CONFIG_COUNT replaced all of it. With maintenance back on, each commit in such a
  script spawned a detached git maintenance run --auto that could outlive the script and
  mutate the fixture while it was being copied, failing tests with a bare ENOENT.

  • the isolation now lives in a global configuration file under
    tests/fixtures/generated-do-not-edit/, written once per process; a script's own
    GIT_CONFIG_COUNT layers on top of it
  • ambient GIT_CONFIG_COUNT is removed from the script environment, as it used to be
    overwritten
  • a script or git() call that writes global configuration fails with a clear message
    and the file is restored, so the mistake stays contained to the offender

Changed (BREAKING)

• raise MSRV to Rust 1.88

  The newly published dua-core 3.3 release used by linked-worktree removal
  requires Rust 1.88, so raise every workspace crate and the advertised badge
  together.

  Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
  release lines that support Rust 1.88.

Commit Statistics

• 22 commits contributed to the release over the course of 32 calendar days.
• 33 days passed between releases.
• 6 commits were understood as conventional.
• 0 issues like '(#ID)' were seen in commit messages

Commit Details