GitoxideLabs/gitoxide gix-index-v0.55.0

gix-index v0.55.0

on GitHub

Bug Fixes

• reject overflowing cache-tree entry counts

  Malformed TREE extensions can declare child entry counts whose sum exceeds u32,
  causing Tree::verify() to panic in debug and fuzz builds. A regression test
  constructs the minimal overflowing sibling pair.

  Use checked addition and return a validation error instead. Git treats malformed
  cache-tree data as invalid in cache_tree_read() (cache-tree.c), which is the
  behavioral baseline.

Chore

• add gix-tix archive ignore; make mtime sensitive test always work.
• Stabilize fixtures on Windows

  • Normalize the precomputed diff fixture assets to LF before writing blobs,
    populating the index, and creating commits. Git for Windows may check these
    assets out with CRLF, which changes their object IDs and adds carriage returns
    to index paths, causing fixture setup to fail at git mv cli c.

  • Prevent Git Bash from rewriting revision arguments before Git sees them, and
    normalize the two pathspec baseline cases where Git for Windows applies native
    path validation to repository-format paths. Exclude a glob baseline whose
    backslash behavior is specific to Git for Windows rather than Git paths.

  • Generate pathological .gitmodules entries as configuration data instead
    of trying to create module directories whose names cannot be represented
    on Windows. Use Git Bash bundled Perl for binary fixture construction so
    regeneration does not depend on a separately installed Python interpreter.

  • Also pass a literal carriage return to sed through Bash ANSI-C quoting when
    normalizing the jj diff assets. Unlike GNU sed, BSD sed does not interpret
    backslash-r in a single-quoted expression, so the previous spelling could remove
    a trailing letter r on macOS instead of stripping CRLF endings.

New Features

• add State::tree_mut()

Commit Statistics

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

Commit Details