NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io
crates.io, #1485 most downloaded on crates.io
A crate of the gitoxide project dealing .gitignore files
Latest stable
0.24.1
Last release 29 days ago
24 Oct 2026
Ships fairly regularly
a new release about every 5 weeks
Nearly every release is documented
notes for 38 of 38 stable releases
1 version withdrawn
withdrawn after publishing
4 years old
39 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
3 commits contributed to the release over the course of 16 calendar days.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
gix index entries also prints attributes.
gix index entries also prints attributes.gix clone and gix fetch with controls for shallow repositories.ein t trace-path know accepts the trace-file alias.stdout on each write, now this is done only once.gix free index entries into gix index entries.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix index entries also prints attributes. (08e8fc2)gix free index entries into gix index entries. (ca8ebdf)gix-worktree (13a070f)index.skipHash (f29f35c)gix clone and gix fetch with controls for shallow repositories. (9723e1a)ein t query (d5616b6)ein t trace-path know accepts the trace-file alias. (f93e964)
</details><csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
0115e90)794eeef)1d7bac7)80f4b03)5fb3dcf)
</details>This release adds the new ein tool query analytics engine, which maintains a database of a git repository as acceleration data structure to run useful
This release adds the new ein tool query analytics engine, which maintains a database of a git repository as acceleration data structure to run useful queries on.
It's nothing more than an MVP, and was inspired by a program to accelerate Git-Heat-Map.
ein tool query - a git analytics engine.
A tool to build and efficiently maintain a database of information contained
in a git repository, preferably the kind of information that is expensive to obtain,
in order to facilitate queries that would be prohibitive without an accelerating
data structure.gix tree entries with rev-spec support.
Previously it wanted a tree-id, now it can derive it itself.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ein tool query - a git analytics engine. (f8cc623)gix tree entries with rev-spec support. (49520d1)<csr-id-4b42e0ce80ae934cae4f102f44c392581758608f/> raise MSRV to Rust 1.88
<!-- agent -->
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.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
37860b3)6356013)a095334)4b42e0c)7e35849)888677a)b8914ff)
</details>re-enable local-time support for all binaries The time improved the way one can opt-in to potential unsoundness in their local time support, forcing t
time improved the way one can opt-in to potential unsoundness
in their local time support, forcing the application to make that
decision at runtime.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
<csr-id-d4b205088a9c137bf39abc43e42d64ad7d839d86/> parse !$ ignore lines as negations unless precious files are enabled
Git has no notion of precious files, so !$foo is an ordinary negation of a
file literally named $foo. gitoxide dropped such lines outright, even with
support_precious off - the mode Lines::new documents as backward-compatible.
Precious support landed in 890efd591 with $ handled unconditionally, which
made rejecting !$ correct at the time. 828e9035a made the parser stateful and
gated the $ branch on support_precious, but the !$ check in the else
branch kept its unconditional form. This applies the same gate to it.
Precious mode is unchanged: !$ is still rejected there.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ebe9095)23388e1)d4b2050)cc3ee80)ab4fcb0)ae8845a)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
git-protocol to gix-protocol (823795a)git-features to gix-features (e2dd68a)git-repository to gix (7bed2a9)add rename() for replacing read-only fixture files
I removed a lot of tests for that, assuming it's trivial enough to get right
and existing tests that use it are proof of function enough.
Git creates read-only commit-graph files. On Windows, this also prevents
replacing them with std::fs::rename(), requiring fixture setup to clear
the destination's read-only attribute first.
Add gix_testtools::rename() to retry permission-denied renames after
clearing that attribute. Other platforms retain std::fs::rename()
behavior. Document that callers must use writable fixtures or fixture
initialization and release memory mappings before replacing backing files.
Trace Bash fixture commands without changing captured baselines
A flaky Windows fetch test failed while generating make_remote_repos.sh,
before the worktree assertions ran. The fixture output stopped after cloning
credential-helpers, leaving no failing command or process exit status to
explain the abort. Expected merge conflicts earlier in the script further
obscured where setup actually failed.
Enable set -x by default for .sh fixtures on Bash 4.1 and newer. Route
traces through BASH_XTRACEFD to a duplicate of the original stderr, so
commands that redirect stderr into fixture baselines do not capture tracing
output. Keep successful fixture generation quiet by retaining the runner's
existing policy of printing captured output only on failure.
Bash 3.2, including the version shipped with macOS, cannot redirect xtrace
independently of stderr. Use an inherited ERR trap there to report the
failed command, script location, and status through the same descriptor.
Include the subprocess exit status in the runner's error on every platform.
Add coverage for silent command lookup failures, unchanged redirected stderr
baselines, and exit statuses in fixture errors. This improves diagnosis; it
does not identify or fix the original Windows flake.
add symlink preflight for Bash fixtures
Careful refackiew, only the tests were mostly waved through as they
are known to be super thorough. Only their style needs checking, which
was fine here.
Fixtures that require symbolic links need to distinguish unavailable symlink
creation on the host from broken fixture setup. Otherwise, tests either fail
on unsupported filesystems or risk hiding unrelated errors when skipping.
Inject gix_testtools_require_symlinks into Bash fixtures to probe creation
of a real link before generating contents. Record the outcome at the fixture
root and stop successfully when links are unavailable. Tests can then use
fixture_has_symlinks() to skip explicitly; missing or malformed results,
unexpected ln exits, copied files, and later setup failures remain errors.
Preserve script arguments and Bash 3.2 source context without exporting the
helper to child shells. Include the prelude in cache keys for fixtures using
the probe, and document archive and writable-fixture constraints.
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.
Make checkout safety fixtures reliable on Windows
The traversal fixture rewrites .git/index to install paths Git would not
normally accept. MSYS sed reads that binary index in text mode, removing
carriage returns from incidental CRLF bytes in its stat data. Variable
timestamps make the resulting corruption intermittent. Setting the mtime to
2000-11-01T12:31:06Z (0x3a000d0a) reproduced the reported
U git/hooks/pre-commit and unresolved-conflict error exactly.
Use Perl with binary standard streams and literal path substitution, which
also works on systems without sed -b. Keep the CRLF-containing timestamp
in every generated repository so text-mode index corruption is exercised
deterministically by the existing checkout safety tests.
The same log's long-path warnings come from a relative XDG_CONFIG_HOME
being reinterpreted after the fixture changes directories. Make the isolated
configuration path absolute, and exercise both absolute and relative fixture
roots by checking that Git still reads the intended attributes after cd.
Validated on Windows with Git 2.55.0.windows.3:
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.
tests/fixtures/generated-do-not-edit/, written once per process; a script's ownGIT_CONFIG_COUNT layers on top of itGIT_CONFIG_COUNT is removed from the script environment, as it used to begit() call that writes global configuration fails with a clear messageraise 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.
rename() for replacing read-only fixture files (9af9145)jtt (40b8e5e)<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
842bc44)cb6ec7d)f0ec710)cf3053a)27aec47)f7d4f33)
</details>15 commits contributed to the release over the course of 28 calendar days.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
10c58bb)9a17734)fe36476)4743361)1980190)e3d5a04)666d441)3a678c9)ab2fee1)2cb17b2)e10d5f6)3675a8d)af9c03d)gix-ignore and gix-attributes fuzz resilient against slow globs (9b77025)adb8328)
</details>gix clone is now permitted without specifying a destination directory. Note that the implementation doesn't take into account potential redirects and
gix clone <url> is now permitted without specifying a destination directory.
Note that the implementation doesn't take into account potential redirects and renames
as it's implemented only with the first URL it sees (not the redirected ones).http.schannelCheckRevokeClippy helped 2 times to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix clone <url> is now permitted without specifying a destination directory. (b81f650)gix progress now usees the configuration tree as basis for data. (ea76bf5)tabled (7aed326)ssh related configuration variables. (3f91088)<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
53f880c)4d5ba23)
</details>This release also fixes compatibility issues that formerly prevented to fetch or clone form https://googlesource.com.
This release also fixes compatibility issues that formerly prevented to fetch or clone form https://googlesource.com.
GIT_(COMMITTER|AUTHOR)_(NAME|EMAIL|DATE) with git configuration.
That way it becomes more obvious where values are coming from.auto-enabled verbosity for gix fetch/clone and add --no-verbose.
I found myself always adding (and having to remember to add) the -v flag
for long-running operations so these should be able to default to a
higher verbosity level.
To counter that, there is a new --no-verbose flag to turn that off.
add --strict option to enforce strict checking of configuration.
gix odb stats to calculate statistics on the object database.
This includes the amount of objects along with a listing of where they are
located.
gix clone --no-tags support.
This is the same as git clone --no-tags.
open::ReplacementObjects is removed in favor of two custom git-configuration flags.
Now it's possible to map the environment variables GIT_REPLACE_REF_BASE and GIT_NO_REPLACE_OBJECTS
to custom git configuration keys which can also be set, namely gitoxide.odb.replaceObjectsRefBase
and gitoxide.odb.noReplaceObjects.
Along with the possibility of disabling the usage of GIT_ prefixed environment variables one
reaches the previous level of control without making object replacement a special case.
represent object cache configuration like GITOXIDE_PACK_CACHE_MEMORY in git-configuration.
That way there is a unified system for how to set values, which may be overridable by configuration
variables or not.
With this changes, the explicit application of environment variables for setting the cache isn't required anymore as everything happens using git-configuration, and automatically, while providing full control like before.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ein t estimate-hours command (4c93de1)gix odb stats to calculate statistics on the object database. (8c9c243)gix clone --no-tags support. (e2b8c5d)gix progress to inform about remote.<name>.tagOpt (3ebb340)gix fetch/clone and add --no-verbose. (9814369)atty to is-terminal (7304bc1)git-repository (c4f68bf)GITOXIDE_PACK_CACHE_MEMORY in git-configuration. (becbd8d)GIT_(COMMITTER|AUTHOR)_(NAME|EMAIL|DATE) with git configuration. (a4ac9cf)open::ReplacementObjects is removed in favor of two custom git-configuration flags. (49f39d6)git-repository (f1a4c8b)--strict option to enforce strict checking of configuration. (aeb4a1d)git-config (1c2e755)allow requiring archived scripted fixtures
Add version-aware fixture loaders:
scripted_fixture_read_only_with_git_version()scripted_fixture_read_only_with_args_with_git_version()Both use normal fixture generation when the installed Git version satisfies
the caller-provided predicate. For incompatible versions, they require an
identity-matching archive, ignore GIX_TEST_IGNORE_ARCHIVES, and return None
instead of running the fixture script when no usable archive exists.
git --version each time a metadata directory is created.expand gix-testtools fixture support
Note that I did only skim through git.rs,
considering the details of the implementation secondary to the outcome.
gix.rs was refactored quite a bit, helping to provide more utilities
in other plumbing crates to help with this 'gix' avoidance.
Add deterministic repository snapshots covering HEAD, references, reachable
commits, every index stage, conflict-free index trees, and exact worktree
contents. Provide a portable form which omits platform-specific filesystem modes
for stable cross-platform assertions.
Add writable Git-version-aware fixture APIs for copy and execute creation modes.
Require archived fixtures when the selected Git is incompatible, without running
unsupported scripts or post-processing.
Use the Git executable selected by gix-path consistently for version checks,
helper commands, and fixture scripts, including PATH selection for scripts.
Harden signing fixtures with command-compatible paths, isolated homes, and
complete SSH key pairs.
git --version each time a metadata directory is created. (4314d09)gix-attributes (e11d7a2)<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
f9fbcba)63b8419)e64e3b8)0396152)2a5db88)e4f380e)444a92b)package.include patterns more specific so they don't match ignored files (c2c917f)29c275e)b1102c2)98bae84)
</details>5 commits contributed to the release.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
4a3d6e9)c389a2c)6a7287c)cargo machete CI job including exclusions (abd0724)f7d0975)
</details>Make reqwest TLS backend configuration easy. We provide the choice of native-tls or rust-tls. If none is provided, the user can configure on their on
Make reqwest TLS backend configuration easy.
We provide the choice of native-tls or rust-tls. If none is
provided, the user can configure on their on similar to how it's done
in git-repository.
Please note that a choice now has to be made or HTTPS will not be available, so use one of…
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
reqwest TLS backend configuration easy. (3ddbd2d)
</details><csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
cbbdef5)562e684)fa302a1)0a333e5)d6c5b9d)
</details>This releases fixes gix fetch so that it is able to clone or fetch pytorch or other repositories on case-insensitive file systems.
This releases fixes gix fetch so that it is able to clone or fetch pytorch or other repositories on case-insensitive file systems.
It's also an attempt to trigger CI to build binary releases.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gitoxide.http.connectTimeout for more control for git clients (2ab80e4)no_proxy environment variable support (f0625de)<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
21fecdf)fbf9c39)
</details>3 commits contributed to the release over the course of 1 calendar day.
<csr-id-6f469a6fea59c88e6c69a5f94b0bc8a5977cb75b/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
bdcce5f)doc_auto_cfg feature to fix docs.rs documentation. (6f469a6)3313233)
</details>gix remote ref-map --show-unmapped-remote-refs. That way it's more obvious to see what was filtered out by ref-specs.
gix remote ref-map --show-unmapped-remote-refs.
That way it's more obvious to see what was filtered out by ref-specs.
It's also great to validate that server-side filtering via ref-prefix will not send refs that are referred to by symbolic refs that are not filtered out. That should be fine as it's all about objects, it's just something to deal with as we may have to deal with symbolic refs that aren't in the set of refs the server sent to us.
diff algorithm is controlled by git configuration diff.algorithm
ein t hours allows to specify the amount of worker threads.
collect stderr and print it afterwards to avoid intersection with line progress.
Previously it would happen that stderr would be printed directly and mix
with the line progress (as in -v) which also prints to stderr.
Now errors are collected and output at the end once the line renderer was already shutdown.
lock_mode from all methods dealing with reference edits.
It is now read from core.filesRefLockTimeout accordingly.gix remote --url in favor of determining the intention similar to git fetchClippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix remote ref-map --show-unmapped-remote-refs. (e973dfe)diff.algorithm (30d32e7)stderr and print it afterwards to avoid intersection with line progress. (3a05328)clone and print once entire clone is done (9a476df)gix clone (23a5e8b)core.checkState (8b2aba1)gix progress (0e9bd41)init.defaultBranch - now used by custom initialization. (4d6d7bb)gix fetch (c47dcc6)gix remote --url in favor of determining the intention similar to git fetch (92bbe33)--url for arbitrary urls when fetching (8c7351c)gix fetch (5b72d27)lock_mode from all methods dealing with reference edits. (3a0fb1b)gix progress show (92e082a)ein t hours allows to specify the amount of worker threads. (20259da)index.version for when we can write V4 indices. (da96d34)extension.worktreeConfig (fe1e646)init.templateDir to gix progress (9fab050)diff.algorithm (b1edb9e)git-diff for a 2x speedup when calculating line changes (296f3b6)gix progress records (b05a2e7)clone. variables (8b804a3)<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
89fb308)4da2927)6cc8464)202bc6d)d64f257)784c046)
</details>Note: Binaries are missing because `release.yml` doesn't run anymore for unknown reason.
Note: Binaries are missing because release.yml doesn't run anymore for unknown reason.
ein tool hours --stat to collect additional statistics per author.
Note that these are expensive and unconditionally use threads to speed
up these computations.ein tool hours -b ignores bots.
For now it only considers bots with names containing [bot].ein tool hours -s was split into -f|--file-stats and -l|line-stats.
That way more information is generated at increasingly high costs.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ref-map sub-command. (94c2b78)gix commands will now load the git installation configuration (23d2dec)gix credential (642e21f)ein tool hours -s was split into -f|--file-stats and -l|line-stats. (3c7c9a7)Progress::counter() feature (0ac4a2c)ein tool hours --stat to collect additional statistics per author. (28c4cae)ein tool hours -b ignores bots. (5d0332f)ein tool hours -s was split into -f|--file-stats and -l|line-stats.
That way more information is generated at increasingly high costs.ein tool hours --stat to collect additional statistics per author.
Note that these are expensive and unconditionally use threads to speed
up these computations.ein tool hours -b ignores bots.
For now it only considers bots with names containing [bot].<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
11851f3)4720666)2237495)f4d8198)ref-map sub-command. (94c2b78)gix commands will now load the git installation configuration (23d2dec)7abc0a3)gix credential (642e21f)26489d1)cf7182e)ein tool hours -b ignores bots. (5d0332f)3773b92)gix index from-tree (2fbd3df)535e967)5c05198)bc64b96)56ba481)791dd66)
</details><csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
5a919c4)65037b5)5f9de52)828e903)648022b)f0ed2cc)c3f06ae)d2b4c44)8d4c4d1)
</details>gix remote refs to list all remote references of a suitable remote. This takes into account either a named remote, or the remote associated with the c
-c/--config in gixgix remote refs to list all remote references of a suitable remote.
This takes into account either a named remote, or the remote associated
with the current branch, or the default remote it could deduce or obtain
from the configuration.gix free remote ref-list in favor of gix remote refs
The functinality is the same, but the latter is built on top of a
repository which is slightly less flexible, but preferable over
maintaining a non-repo version.Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix free remote ref-list in favor of gix remote refs (dda9957)-c/--config in gix (45a30f0)gix remote refs to list all remote references of a suitable remote. (5d6d5ca)gix remote refs without any implementation. (f8f1249)<csr-id-f7f136dbe4f86e7dee1d54835c420ec07c96cd78/>
-c/--config in gixgix remote refs to list all remote references of a suitable remote.
This takes into account either a named remote, or the remote associated
with the current branch, or the default remote it could deduce or obtain
from the configuration.gix free remote ref-list in favor of gix remote refs
The functionality is the same, but the latter is built on top of a
repository which is slightly less flexible, but preferable over
maintaining a non-repo version.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix config. (19c1746)gix free remote ref-list in favor of gix remote refs (dda9957)-c/--config in gix (45a30f0)e0be6e9)df3cf18)gix remote refs to list all remote references of a suitable remote. (5d6d5ca)db4df25)gix remote refs without any implementation. (f8f1249)39d585d)bb6813a)e2ee3de)31c2351)b1c40b0)f7f136d)bd5f3e8)
</details><csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
e104545)5f7f805)631f07a)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
cc5b696)49fa9f3)db0b095)0bf84db)b5e9059)68e6b2e)420e730)
</details>Invert behaviour to open::Options::strict_config(), with lenient being the default. This means API users will get libgit2 behaviour but commands like
open::Options::strict_config(), with lenient being the default.
This means API users will get libgit2 behaviour but commands like gix can
change options to emulate git behaviour.--cat-file flag for gix rev parse to cat instead of resolving.gix rev previous-branches subcommandein tools to ein tool for as it's more intuitivegix rev resolve --explain<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
--cat-file flag for gix rev parse to cat instead of resolving. (b83f6bd)gix rev resolve --explain (c5846e0)gix rev previous-branches subcommand (e972aad)gix (b838202)gix-config can be lenient. (6a9c58f)open::Options::strict_config(), with lenient being the default. (0235111)ein tools to ein tool for as it's more intuitive (edf73dd)open::Options::strict_config(), with lenient being the default.
This means API users will get libgit2 behaviour but commands like gix can
change options to emulate git behaviour.--cat-file flag for gix rev parse to cat instead of resolving.gix rev previous-branches subcommandein tools to ein tool for as it's more intuitivegix rev resolve --explain<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
dbaff13)gix-config can be lenient. (6a9c58f)open::Options::strict_config(), with lenient being the default. (0235111)c4bf958)805f432)ein tools to ein tool for as it's more intuitive (edf73dd)a938986)a6d79e3)2f506c7)ce885ad)9b9ea02)6da8250)7b61506)47724c0)4e7b343)e9fcb70)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
b41312b)38dff41)8df0db2)
</details>keep sanitized reference names nonempty and be more Git conformant
keep sanitized reference names nonempty and be more Git conformant
Replace leading dots before stripping repeated .lock suffixes, matching Git so
.lock.lock becomes -lock instead of losing its name. Handle empty sanitized
output without indexing it.
Keep name_partial_or_sanitize() returning BString and guarantee a nonempty
valid partial reference name. Empty or slash-only input falls back to -;
document this Gitoxide-specific behavior so callers need no empty-result
handling.
gix config with section and sub-section filtering.gix config lists all entries of all configuration files git considers.
Filters allow to narrow down the output.Clippy helped 3 times to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
--show-ignore-patterns to gix repo exclude query (09f904b)exclude query (9cb8385)gix repo exclude query (a331314)gix restructuring (59b95c9)gix config with section and sub-section filtering. (eda39ec)gix config lists all entries of all configuration files git considers. (d99453e)git_path (4420ae9)gix repo rev explain (12e6277)gix config with section and sub-section filtering.gix config lists all entries of all configuration files git considers.
Filters allow to narrow down the output.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 3 times to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
0c597fe)--show-ignore-patterns to gix repo exclude query (09f904b)exclude query (9cb8385)7d98b21)cb56f12)3ff991d)gix repo exclude query (a331314)50ff7aa)gix restructuring (59b95c9)gix config with section and sub-section filtering. (eda39ec)gix config lists all entries of all configuration files git considers. (d99453e)a437abe)8e5b796)5cf08ce)0ed65da)38a8350)72876f1)ac7d99a)c9c78e8)8967fcd)f99c3b2)83585bd)1cdecbc)141c5f1)f4e1810)faaf791)git_path (4420ae9)afecb63)48b3f4a)085e76b)0700b09)89ea12b)0e9df36)229dc91)41ea8ba)05eb340)7cb1972)251b6df)98da8ba)056e8d2)fdec111)4086335)e90d3fd)
</details><csr-id-17835bccb066bbc47cc137e8ec5d9fe7d5665af0/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
dea106a)1f6390c)7ec21bb)rust-version to 1.70 (17835bc)e8b3b41)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
4000197)9d627bb)4145d2a)db5c9cf)
</details>preserve validation classifications after error conversion
ValidationError marker from reference, tag, submodule,gix::Error, including optional reference lookups.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.
gix repo commit describe
It supports typical but basic flags mostly similar to the ones in git.<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
gix repo commit describe (7e99e6a)gix repo describe plumbing command (2d6ccef)
</details><csr-id-64ff0a77062d35add1a2dd422bb61075647d1a36/>
<csr-id-17573779688e755a786546d5e42ab533088cd726/> remove all workspace dependencies The problem is that with them, we don't notice anymore if the crate changes, because a dependency changes. That also means that older versions of the dependency may stay even though some other crates might pick up a newer version.
Ultimately, this will lead to drift and subtle incompatibilities.
We declare this breaking to enforce a proper re-release.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
3f7e8ee)795962b)64ff0a7)37c1e4c)af03832)93e86f1)012a754)649f588)beba720)37ba461)2e0ce50)46cd1ae)1757377)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
f2b522d)a65a17f)d19af16)0f25841)2e00b5e)unicode-bom (89d77dc)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 1 time to make code idiomatic.
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
/ behaves, and * + excludes (4f67be4)6232824)a1b73a6)0470df3)99c00cc)b4dba1c)15f1cf7)8d89b86)1dfa90d)tar files (dcab79a)9fa1054)2f9f0ac)acc1331)9c65d98)68cbea8)2cefe77)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
b050327)52c3bbd)3e5c974)f8ce3d0)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
45b4470)f2e111f)b8cba96)
</details>Adapt to changes in git-features which change Send + Sync to Send + Clone. This happens to allow non-sync implementations (i.e. thread-local), along w
Adapt to changes in git-features which change Send + Sync to Send + Clone. This happens to allow non-sync implementations (i.e. thread-local), along with Sync ones
which usually are Clone too as they are passed by immutable reference (which is Clone + Copy).
Option<impl Progress> in favor of impl ProgressArc around should_interrupt flagindex::verify::Mode::* variants
The hash is repository defined and not hard-codedgix mailmap verify commandein find --debug to learn why it is slow<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
Option<impl Progress> in favor of impl Progress (bf04644)Arc around should_interrupt flag (d851bed)index::verify::Mode::* variants (c2679a0)gix mailmap verify command (384ed66)ein find --debug to learn why it is slow (70109be)<csr-id-890efd59147768f37538fe0dfc0097a25e43f43d/> Add experimental notion of precious files. Precious files are ignored files, but those that are not expendable. By default, all ignored files are expendable, but now it's possible to declare ignored files as precious, meaning they will not be removed just like untracked files.
See [the technical document][1] for details.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
eb6aa8f)6a2e0be)b6c04c8)c3983c6)890efd5)
</details>safely split commands and ignore shebang options
safely split commands and ignore shebang options
Command preparation previously rejected every first word containing an equals
sign, so valid environment prefixes required a shell while executable names
such as tool=name could be misinterpreted as assignment-only commands. Its UTF-8
conversion also made the direct-versus-shell decision depend on encoding.
Git for Windows uses only the interpreter path from a shebang. Parsing the
suffix as shell words invented incompatible semantics and could let executable
contents supply additional interpreter options.
This provides two major fixes:
Reuse the parser in gix-diff and cover its full byte-input domain with focused
unit tests and a dedicated fuzz target.
Store the required command in Outcome::command, reserve Outcome::args for
actual arguments, and reject command lines that produce no executable. Command
preparation can now consume the parser result directly without another emptiness
check or first-element extraction.
The command-line parser is consumed primarily by process-launch code, yet it
returned byte strings that every caller had to convert before constructing
std::process::Command.
Return OsString for the required command and its arguments so callers can use
them directly while preserving arbitrary Unix bytes. Reject values that the host
cannot represent instead of risking a conversion panic; environment assignments
remain byte-oriented for parsing.
Manual argument splitting moved leading assignments into the process environment
and spawned the parsed program directly. On Windows, Rust's lookup can fall
outside the assigned PATH and cannot launch extensionless scripts through their
shebang.
Keep assignment-prefixed commands on the shell path on Windows while retaining
manual splitting for other commands and platforms.
invoke existing absolute paths directly
Shell detection treated metacharacters in every command as evidence that a
shell was needed. This caused resolved executable paths, notably Git for Windows
programs under Program Files, to be parsed as command text and split at spaces.
Recognize existing absolute files as already-resolved programs and bypass shell
detection for them.
Requiring an absolute path avoids promoting a relative path that happens to name
a file in the repository to a program and accidentally executing it.
<csr-id-3bd09ef120945a9669321ea856db4079a5dab930/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
972241f)8c492d7)rust-version manifest field back to 1.65. (3bd09ef)
</details>This release pins beta versions of clap to avoid it to automatically fetch the latest one during installation.
This release pins beta versions of clap to avoid it to automatically fetch the latest one
during installation.
This is made possible due to clap itself pinning its dependency
to the clap-derive crate.
This release pins beta versions of clap to avoid it to automatically fetch the latest one
during installation.
This is made possible due to clap itself pinning its dependency
to the clap-derive crate.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
<csr-id-aea89c3ad52f1a800abb620e9a4701bdf904ff7d/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
e1aae19)e78a92b)4454c9d)aea89c3)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
55d386a)d3dcbe5)5a0d93e)bb3224c)c0e72fb)b65a80b)
</details>A first usable version of git-repository to make using gitoxide from your applications so much easier. It serves as a one-stop shop for application de
A first usable version of git-repository to make using gitoxide from your applications so much easier. It serves as a one-stop shop for application developers without sacrificing performance by default while making common use-cases more convenient.
git-repository as hub crate for application development with focus on usability without sacrificing any knob to tune performance.async for git-packetline, git-transport and git-protocol for fully async git clients, along with the light-async feature toggle to build a gixp pack-receive with an async client instead of a blocking one.gixp pack-create with the -s/--statistics flag to have data indicating the cost of the operation. Currently it's doing a lot of work that has to be avoided in order to be useable in production and the numbers underline that. Future iterations will cause key metrics to go down.git-tempfile crategit-lock crategit-ref crate with complete loose-ref, packed-ref and transaction support.git.git-object parsing is a few percent faster thanks a reworked error handling for objects. By default, error collection is disabled entirely making the error case zero-sized. If needed, verbose and stacked errors can be turned on using a feature toggle for applications who expect repositories with malformed objects and need detailed diagnostics.Full Changelog: https://github.com/Byron/gitoxide/compare/v0.8.4...v0.9.0
A first usable version of gix to make using gitoxide from your applications so much easier. It serves as a one-stop shop for application developers without sacrificing performance by default while making common use-cases more convenient.
gix as hub crate for application development with focus on usability without sacrificing any knob to tune performance.async for gix-packetline, gix-transport and gix-protocol for fully async git clients, along with the light-async feature toggle to build a gix pack-receive with an async client instead of a blocking one.gix pack-create with the -s/--statistics flag to have data indicating the cost of the operation. Currently it's doing a lot of work that has to be avoided in order to be useable in production and the numbers underline that. Future iterations will cause key metrics to go down.gix-tempfile crategix-lock crategix-ref crate with complete loose-ref, packed-ref and transaction support.git.gix-object parsing is a few percent faster thanks a reworked error handling for objects. By default, error collection is disabled entirely making the error case zero-sized. If needed, verbose and stacked errors can be turned on using a feature toggle for applications who expect repositories with malformed objects and need detailed diagnostics.<csr-read-only-do-not-edit/>
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
68e5432)1347a54)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
7891fb1)8a60d5b)
</details>The last release was nearly 5 months ago, and a lot happened since then.
The last release was nearly 5 months ago, and a lot happened since then.
First of all, gitoxide is now sponsored which allows me to make developing it my full-time job. This job I intend to perform until it is done or I drop dead (of old age), whatever comes first. This will also be beneficial for another project of mine, GitPython, which will eventually become a front-end to gitoxide using the marvellous PyO3.
Or in other words, this is the beginning of an exciting journey 😎.
gix tool estimate-hoursWith gix tool estimate-hours (or gix t h) you can now apply the git-hours algorithm to repositories of any size and estimate the time it would take a person to recreate its contents. It can do the linux kernel in 7.5s, even though it's not (yet) beating git shortlog by a small margin.
gix tool organize and gix tool findDo you find yourself with 100's of repositories in your dev directory because you keep cloning them just to have a look and keep them for reference? And by now, all that seems a bit messy and you wish there is a better way?
The organize subcommand reads the origin remote's URL and suggests to place the repository in its path. For example, the repository cloned from https://github.com/byron/gitoxide at ~/dev/gitoxide could be moved to ~/dev/github.com/byron/gitoxide. Actually perform the operation by passing --execute as well.
The sibling command find uses the same repository discovery algorithm used by organize and lists the repository paths. This can be useful for building shell utilities to quickly jump to repositories in this new location.
Here is what works for me from ~/.zshrc.
function select-repo() {
local root=~/dev
echo -n $root/
{
cd $root
gix t find
} | sk -q "$1"
}
function cd-repo() {
cd "$(select-repo $@)"
}
alias or="cd-repo"
Thanks to a fantastic PR a lot of code could be simplified into something that's easier to understand and contains only 2 one-liners of unsafe. As a side-effect, certain operations involving decoding entire packs are now significantly faster.
There shall also be an honorable mention which makes traversing the android-base pack faster.
Even though I keep management and planning very lean, there are now a few pointers which should help to find tasks to tackle and make your first contribution. If you were on the fence, now might be the time to join, and if something is holding you back, please let me know as well.
Please refer to the installation instructions in the README.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
Clippy helped 3 times to make code idiomatic.
dyn trait where possible.
This reduces compile time due to avoiding duplication.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
8bd0456)375db06)dynification (f658fcc)dyn trait where possible. (072ee32)363ee77)
</details>These are created to account for breaking changes within the dependency graph of gitoxide crates. Due to some blunders in the past the version on crat…
Maintenance release without any new features.
These are created to account for breaking changes within the dependency graph of
gitoxide crates. Due to some blunders in the past the version on crates.io
could not be installed anymore.
This was eventually fixed with new minor releases across the ecosystem.
Finally, yet another breaking change due to the introduction of the gix-hash
crate to break a dependency cycle between gix-object and gix-features caused
yet another maintenance release.
<csr-id-229bd4899213f749a7cc124aa2b82a1368fba40f/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
6c62e74)30b2761)f23ea88)229bd48)9f4dfe0)gix-glob (f564fed)gix-glob (a943647)4604f83)6b4a303)ef8ccd9)
</details>Document the gix-utils/prodash workaround and guard auditable builds
Document the gix-utils/prodash workaround and guard auditable builds
cargo-auditable reconstructs enabled features from Cargo’s rustc arguments
and replays them into workspace-wide cargo metadata. The root package’s
implicit prodash feature also matches gix-utils’ optional dependency,
despite dep:prodash suppressing its implicit feature. Cargo then rejects the
request for the nonexistent gix-utils/prodash feature.
Explain why the explicit alias is a tooling compatibility workaround, link
the upstream Cargo and cargo-auditable issues, and document a metadata
reproduction and how to reassess removal.
Add just check-auditable and a blocking CI job using stable Rust and
cargo-auditable 0.7.6. Test an actual auditable build of the small
configuration rather than requiring the alias itself, so an upstream fix can
allow the workaround to be removed without rewriting the check.
gix-utils/prodash workaround and guard auditable builds (6a262bc)skip classification markers in flattened error chains
ClassificationMarker supplies recovery metadata without a diagnostic of its
own. Flattened error chains exposed these markers as extra causes: an
intrinsically classified leaf gained a trailing Validation or Conflict,
and a source-bearing tag repeated the diagnostic of the error it wrapped.
Skip markers during ChainedError::source() traversal and promote the first
real diagnostic when converting a marker-rooted Exn to anyhow::Error.
Align the public Error source chain in auto-chain-error mode with its
existing display promotion so tagged roots appear only once. Keep markers
stored internally for classification and tree recovery, and preserve the
root display fallback for marker-only errors.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
0062971)107a64e)16295b5)c4cc5f2)5cb3589)2fc66b5)9064ea3)
</details>avoid redundant Unicode precomposition work
avoid redundant Unicode precomposition work
We now preserve macOS conversion failures per filename, but splitting
every path adds work even for ASCII. In the initial benchmark, ASCII paths
took about 2.6-2.8 times as long as before. The existing is_nfc()
check can also perform a full NFC conversion before our compatibility
composer performs its own decomposition and composition.
Use is_nfc_quick() and detect non-BMP characters through the same iterator.
Only scan its unvisited suffix if quick-check stops early. ASCII strings
return immediately; ASCII paths also avoid UTF-8 validation and splitting.
Process BMP-only paths together, reserving component splitting for paths
with conversion failures. Specialize filename and path handling at compile
time to keep the path fallback out of the filename loop.
Skip combining-class and composition lookups for ASCII starters, use byte
lengths for buffer capacities instead of counting characters, and reserve
the output string before encoding it. Keep noncanonical mark order, Hangul
composition, component-local fallback, and the original Cow when unchanged.
The capacity estimate can reserve more space than the previous character
count. Inconclusive NFC checks can now use a temporary buffer even if the
result is unchanged; the benchmark explicitly covers that case. There are
no new runtime dependencies; Criterion is already used in this workspace.
Add a Criterion benchmark covering filenames and paths with ASCII, NFC,
NFD, Hangul, noncanonical marks, and mixed emoji/decomposed components.
| Case | Original HEAD median (ns) | This commit median (ns) |
|---|---|---|
filename/ascii |
6.46 | 2.55 |
filename/emoji_first |
63.54 | 3.17 |
filename/emoji_last |
57.95 | 15.80 |
filename/hangul_nfc |
12.20 | 11.88 |
filename/hangul_nfd |
141.87 | 70.28 |
filename/nfc |
16.60 | 15.78 |
filename/nfc_quick_check_maybe |
70.32 | 32.75 |
filename/nfc_with_mark |
11.03 | 11.89 |
filename/nfd |
303.23 | 70.96 |
filename/noncanonical_marks |
46.98 | 32.58 |
filename/several_nfd |
139.12 | 58.56 |
path/ascii |
34.71 | 2.69 |
path/ascii_long |
98.55 | 4.23 |
path/mixed |
403.60 | 134.15 |
path/nfc |
50.75 | 26.13 |
path/nfd |
378.76 | 234.88 |
path/reported |
106.27 | 37.88 |
path/several_nfd |
343.42 | 101.15 |
The NFC string with an uncomposable mark costs about 0.9 ns more; the
other measured cases improved. These are normalization microbenchmarks,
not measurements of complete status operations.
To compare subsequent changes:
cargo bench -p gix-utils --bench precompose -- --save-baseline before --sample-size 100 --warm-up-time 1 --measurement-time 2 --noplot
# Apply the change being measured, then:
cargo bench -p gix-utils --bench precompose -- --baseline before --sample-size 100 --warm-up-time 1 --measurement-time 2 --noplotpreserve filenames rejected by macOS precomposition
The original Starship report states that a tracked filename
containing both an emoji and a decomposed umlaut is reported
as untracked by gix status.
Git's macOS UTF-8-MAC conversion rejects characters outside the Basic
Multilingual Plane. When conversion fails, Git keeps the entire original
input, including any decomposed umlauts before or after the rejected
character. Our precomposition instead changed those umlauts, preventing
the directory walk from matching Git's index entries.
Preserve inputs containing non-BMP characters in the shared precomposition
helper. Apply that rule separately to each filesystem-path component,
preserving path separators and borrowing unchanged paths. Reference packing
and lookup also use component-wise precomposition, consistent with loose
reference iteration.
Explicit file roots in the directory walk use the same path helper, so
their emitted spelling agrees with ordinary traversal beneath emoji
directories. Extend the existing root-precomposition test to cover an
emoji parent and an emoji filename, with precomposition enabled and disabled.
An emoji outside a reference name must not suppress that name's
precomposition: otherwise loose and packed versions of an umlaut branch
can be emitted twice. Cover that review finding, packing and lookup below
an emoji component, both emoji/umlaut orderings, another supplementary-plane
character, the reported Teaching/🎥 Überwachung im digitalen Zeitalter.md
filename, and BMP-only controls.
Restore the requested reference spelling after lookup instead of
decomposing the entire returned name. Whole-name decomposition could alter
an untouched emoji/umlaut component and make the returned name unusable
for another lookup or deletion. Cover mixed composition, loose and packed
references, full names, and worktree-qualified lookup round trips.
Keep canonical pseudo-ref names when precomposition changes their
classification, including worktree-qualified pseudo-refs.
Both the helper regression and macOS status regression failed before the
fix and now pass, as do the reference regressions added for the review
finding. Validated the gix-utils, gix-fs, gix-dir, gix-status, and
gix-ref suites, the gix status tests with default features and with
--no-default-features --features basic,extras,comfort, targeted Clippy
with warnings denied, and cargo fmt --all -- --check.
Git reference: Apple Git 2.54.0 with core.precomposeUnicode=true leaves
the repository clean. /usr/bin/iconv -f UTF-8-MAC -t UTF-8 rejects these
non-BMP characters. compat/precompose_utf8.c::precompose_utf8_readdir()
and precompose_string_if_needed() at
d38352cd43ab9745686d697872408bc3249a153f retain the original input on
conversion failure.
Maintenance release without any new features.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
9cb09b2)5c7b52d)2571113)aacf0f0)ca5b801)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
4aca8c2)68ae3ff)c70e54f)e4dded0)
</details>fix installation via cargo install
cargo install<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
69c6a36)c143cf4)gix-path across all crates (73c1292)
</details>add git_is_space() It's very niche but needed for correctness in globs and git-config parsing.
git_is_space()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.
move the sirocco feature to sirocco 0.2
sirocco 0.2 decodes into a buffer the caller owns, in one call or many,
so it now handles all zlib decompression with the feature, with no
fallback to zlib-rs:
Inflate::once() and Inflate::prefix() decode with sirocco. Asirocco's partial output.Inflate::rest() continues the stream prefix() started, whichInflate::state.zlib-rs as before.stream::inflate::Measure uses sirocco::inflate::Scanner.sirocco's errors map to the classes and messages zlib-rs produces,
corruption as "Invalid input data" and a preset dictionary as a
validation error.
add the sirocco feature to decompress with sirocco
sirocco is a pure-Rust DEFLATE/zlib decompressor that is faster than zlib-rs
on whole buffers, and can find where a stream ends without producing its output.
With the feature enabled:
Inflate::once() decodes whole streams with sirocco, and falls back to zlib-rsInflate::prefix() always uses zlib-rs, for callers that only want thegix-pack and the loose object header.stream::inflate::Measure finds the compressed and decompressed size of aBufRead. BytesToEntriesIter uses it instead of decompressingio::sink(). With sirocco, the decompressed bytes aren't produced, so thezlib-rs is still used for everything else, including all compression.
The gix crate exposes it as zlib-sirocco, and the fast feature of gitoxide
enables it for the gix and ein binaries. sirocco requires Rust 1.89.
hide the Inflate backend and align stream lifecycles
Spend a lot of time with this one and massaged it into place, overall simplifying
a little and adding test-coverage (that I am sure is already in Sirocco but doppelt
haelt besser).
The public Inflate::state field exposed a zlib-rs decoder even when
sirocco handled all decoding. Make backend state private and retain only
the selected implementation, avoiding an unused zlib-rs allocation when
sirocco is enabled.
Inflate backend and align stream lifecycles (0ed7c8c)sirocco feature to sirocco 0.2 (2b4faf9)sirocco feature to decompress with sirocco (95a0b14)gixp --verbose pack-receive https://github.com/git/git --refs-directory out/all-refs out
gixp --verbose remote-ref-list https://github.com/torvalds/linuxFor some reason these are currently broken and I don't want to spend time on fixing it right now. PRs to fix this are very welcome.
remote-ref-list and pack-receive subcommands to gixindex-from-pack to pack-index-from-data<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
fb1f048)445be27)46a3511)c06d819)487d06d)2fcb557)b38290e)35e26fc)f90b92f)161e7df)5ea49c8)40a6412)386673c)b4a6e16)
</details>A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ea9f942)18b0a37)aa16c8c)4f635fc)
</details>5 commits contributed to the release over the course of 13 calendar days.
pack-explode and pack-index-from-data sub-commandspack-verifyMany small and possibly breaking changes are not mentioned here.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
34b2373)e71da0f)f59f66e)763d7ca)3a4faec)1931575)181d69c)e509373)d7591e2)c0352c2)91ba045)bca7ce2)584350a)395c7e7)8812e91)657aa2c)1e2ec7e)cc147bc)43c7fd1)9660bbf)44b8221)665696f)ee45c7f)0a33b24)29b9c23)adbc82c)0d31ad1)1805d64)0bcb790)f66b116)f932256)ec8c48a)d3c00c8)5e23137)93a9b30)aeb8778)bb45c3d)ec40e09)bcb275e)41f38c4)a7cfac8)afae684)fbb9f98)2888f1b)f98c5b1)7c5d8b8)
</details>gix::index::search::Match.
It was originally meant to be general also for attribute matches,
but that wasn't possible after all.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
9a9fa96)8f15cec)3ef5c90)9375cd7)facaaf6)a849da8)gix::index::search::Match. (e431f54)
</details>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 t
migrate errors to gix-error
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.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
7ebc9f7)0135158)43ebaf2)
</details>Initial release with pack-verify
pack-verify<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
c68d9ab)48c4bbd)1f1b725)cce71aa)f276a05)4aa8022)e2a7bdd)41e01a5)e98e7c2)5fff552)0cc1bf2)aac0d34)af02b46)a4d978c)a1a0b13)5acecc5)1f9bc03)fce7035)b3780f8)13cd8ce)ac490c2)6794300)122d69f)6adf615)5b4979c)7add82c)3bf3321)c416152)60eaea0)caa883b)026a0dd)30925e6)67026e4)aaf4825)b820717)da3ae1c)b1e51d6)0fbba9f)ba6a8ef)f01c298)b09b4e1)0ac9c5a)8c0e0b5)7cec2b6)41f4bce)1179ac1)3ca2c59)aa8efdd)eb7388c)417c34b)87c8a2e)2aa0857)57737c2)c3d319f)
</details><csr-id-b83ee366a3c65c717beb587ad809268f1c54b8ad/> Rename serde1 cargo feature to serde and use the weak-deps cargo capability.
With it it's possible to not automatically declare all optional dependencies externally visible
features, and thus re-use feature names that oterwise are also a crate name.
Previously I thought that serde1 is for future-proofing and supporting multiple serde versions
at the same time. However, it's most definitely a burden I wouldn't want anyway, so using
serde seems to be the way to go into the future.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
serde1 cargo feature to serde and use the weak-deps cargo capability. (b83ee36)91134a1)30a1a71)8dbd0a6)5d2b5d0)cdef398)19338d9)gix-fs crate to consolidate all filesystem utilities (f8cc33c)23ee47f)3d47919)gix-ignore crate with the contents moved and adapted from gix-attributes. (fc28701)
</details>One column per quarter.