GitoxideLabs/gitoxide gix-config-v0.61.0

gix-config v0.61.0

on GitHub

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.

• track semantic emptiness across continuations
  A bunch of refactoring, and more white-space and continuation related conformance with Git.

  Quote delimiters do not append bytes to Git's parsed value, so a raw non-empty
  continuation chunk may still leave the value empty. Track logical bytes and open
  quote state when deciding whether continuation indentation is significant.

• don't indent a value that starts on a continuation line
  git discards whitespace for as long as the value it has accumulated is
  still empty, so the indentation of the line a value starts on is
  insignificant — whether that is the line with the = on it, or a later
  line reached through a \ continuation. parse::from_bytes::value() only
  applied this to the first line: after a continuation it set value_start
  to the first byte of the next line, so the indentation became part of the
  value.

  Given this .git/config:

  [alias]
  	lg = \
  		log --oneline --graph

  git config --get alias.lg reports log --oneline --graph, while
  File::raw_value("alias.lg") reported \t\tlog --oneline --graph. The
  leading tabs are silently carried into whatever runs the alias, and the
  same happens to any continued value written in this shape, such as a
  core.pager set over two lines.

  value() now emits that indentation as Event::Whitespace for as long as
  every chunk seen so far has been empty — the very sequence that
  Event::ValueNotDone already documents ("A Newline event usually
  follows, followed by either ValueDone, Whitespace, or another
  ValueNotDone"). Because the events keep the bytes, to_bstring() still
  round-trips the file unchanged, and every consumer already ignores
  Whitespace when concatenating value chunks.

  Indentation that follows actual content is untouched, matching git:
  k = abc\ + \n\tdef stays abc\tdef, and multi-line aliases that begin
  on the = line keep their interior whitespace.

Changed (BREAKING)

• migrate errors to gix-error

  rubberstamp

• 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

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

Commit Details