GitoxideLabs/gitoxide gix-glob-v0.27.1

gix-glob v0.27.1

on GitHub

Chore

• 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 Pattern::has_wildcard()

  The first_wildcard_pos field marks where raw literal-prefix matching must stop,
  so it includes escape introducers as well as wildcard operators. Consumers
  therefore cannot use it to determine whether a pattern actually contains
  wildcard syntax.

  Add Pattern::has_wildcard() to detect asterisk, question-mark, and bracket
  operators independently of literal-prefix handling. Escaped operators still
  classify the pattern as containing wildcards, while an escape by itself does
  not.

Commit Statistics

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

Commit Details