NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io
crates.io, #1282 most downloaded on crates.io
Utilities shared by the gitoxide crates
Latest stable
0.5.2
Last release 29 days ago
24 Oct 2026
Release timing varies
gaps range from 8 days to 6 months
Nearly every release is documented
notes for 27 of 27 stable releases
1 version withdrawn
withdrawn after publishing
4 years old
28 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 13 calendar days.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
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.
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><csr-id-fbcb26286297b76f90a39c703a40259bd72e261b/> avoid redundant Unicode precomposition work
<!-- agent -->
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 --noplot
<csr-id-4f7454a4a1a11a2555215eb414c048df9a6cab9f/> preserve filenames rejected by macOS precomposition
<!-- agent -->
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.
Refs https://github.com/starship/starship/issues/6881
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
0115e90)794eeef)1d7bac7)3f6fcda)fbcb262)4f7454a)5fb3dcf)
</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>git_is_space()
It's very niche but needed for correctness in globs and git-config parsing.<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)65c5dfe)git_is_space() (fde4d7d)a095334)4b42e0c)b8914ff)
</details>preserve combining-mark order when precomposing paths <!-- agent --> On macOS, gix status reported a tracked dua-cli fixture as untracked while git st
<csr-id-234181b199b533594ec9e41f3623e399d414e9e1/> preserve combining-mark order when precomposing paths <!-- agent --> On macOS, gix status reported a tracked dua-cli fixture as untracked while git status was clean. The filename contains valid combining marks in noncanonical order; full NFC normalization reordered them before the directory walk looked the path up in the index.
Recompose filesystem-decomposed characters without canonical reordering, preserving non-composable combining-mark byte order. Cover both the helper behavior and a Git-created index entry in the directory walk.
Git baseline: Git 2.50.1 uses UTF-8-MAC to UTF-8 iconv conversion in compat/precompose_utf8.c, with directory-read coverage in t/t3910-mac-os-precompose.sh. That conversion leaves the reported combining-mark order unchanged.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
add AsBStr utility trait. It makes taking &BStr generically much easier and convenient.
AsBStrOpt traitAsBStr utility trait.
It makes taking &BStr generically much easier and convenient.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
f0ec710)5982dfe)AsBStrOpt trait (420f228)55b5158)AsBStr utility trait. (1965eb0)cf3053a)
</details>add rng module to gix-utils for better inter-process seeding This should avoid flaky capability tests of multiple process acting on the same repositor
rng module to gix-utils for better inter-process seeding
This should avoid flaky capability tests of multiple process acting on the
same repository.<csr-id-efa5ffcf9a2acdcaf7877ef350f24cf120854334/> seed fast pseudo-random numbers to differ across processes
gix-utils and gix-fs drew fast pseudo-random numbers from fastrand's
global generators, whose per-thread seed is derived only from values that
can coincide between separate processes (notably small thread IDs). Two
concurrently running processes could therefore produce identical sequences,
which weakens backoff jitter (meant to avoid a thundering herd of retries)
and can make the filesystem capability probes collide on their temporary
file names -- e.g. spuriously reporting that symlinks are unsupported (#1789).
Add a gix_utils::rng module that draws from a per-thread fastrand::Rng
seeded from a high-entropy OS source via getrandom, and route the affected
call sites (backoff jitter and the gix-fs capability probes) through it.
getrandom is a target-specific dependency that is excluded on
wasm32-unknown-unknown, which has no entropy backend by default and runs a
single process; there a best-effort seed is used that deliberately avoids
Instant::now() (which panics on that target).
For https://github.com/GitoxideLabs/gitoxide/issues/1816
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
27aec47)386f31a)rng module to gix-utils for better inter-process seeding (96ead72)bf4b474)efa5ffc)f7d4f33)
</details>5 commits contributed to the release over the course of 2 calendar days.
.cargo_vcs_info.json optional in gix-imara-diff provenance test (2afec0e)<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
10c58bb)ab2fee1)2cb17b2)e10d5f6)3675a8d)4d5ba23)
</details>add ergonomic test errors and string comparisons
<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)2a5db88)e4f380e)444a92b)package.include patterns more specific so they don't match ignored files (c2c917f)29c275e)b1102c2)3313233)
</details>add BoxedResultExt for boxed errors
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
89fb308)4da2927)6cc8464)20b7c20)0e5d961)8d4c4d1)
</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><csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
e104545)5f7f805)631f07a)
</details>gate experimental APIs with introduction dates
gate experimental APIs with introduction dates
A stable API needs to retain internal access to experimental items while making
those items an explicit opt-in for downstream consumers. Cargo feature unification
also means API checks must distinguish experimental members even when compiled
with the feature enabled.
Add unstable for items, inherent methods and trait implementations, plus
unstable_fields for selected public fields. Disabled gates retain crate-private
access where Rust permits it; trait implementations are omitted instead. Support
file-backed modules on Rust 1.88 through inline bodies with include!;
applying the attribute directly to pub mod name; requires Rust 1.99.
Require since = "YYYY-MM-DD" with the item's introduction date from Git history.
Validate calendar dates and include them in the generated instability marker.
Keep reason optional and nonempty when supplied, for explanations beyond the
signature or the fact that an item is experimental.
Cover visibility, fields, trait implementations, documentation, missing and
malformed dates, leap years and centuries, and invalid or duplicate arguments.
The fixtures use their introduction dates from Git history.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
db0b095)0bf84db)3b1bef7)c3c6504)b5e9059)68e6b2e)420e730)
</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.
<csr-id-d737c4a6856c01a54c3ec1eea9ee4b70d76f67ab/> Rename Exponential backoff to Quadratic
The gix_utils::backoff::Exponential type actually implemented
quadratic, not exponential, backoff. This renames it from
Exponential to Quadratic.
In exponential backoff, delays are a fixed base, often 2, raised to a power of a number that increases by one with each attempt. When the number that increases by one with each attempt is the base, raised to a fixed power, that is quadratic backoff.
The intended behavior here was quadratic, as implemented. For
example, in the tests, EXPECTED_TILL_SECOND lists the values 1,
4, 9, 16, 25, 36, 49, 64, 81, 100, and so on, which are ascending
squares. If they were an exponential sequence, then they would look
like 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, and so on.
Thus, it is only the named that needed to be changed: the implementation was already as intended.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
b41312b)38dff41)ffb73b5)Exponential backoff to Quadratic (d737c4a)8df0db2)
</details>5 commits contributed to the release.
<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)db5c9cf)
</details>10 commits contributed to the release over the course of 123 calendar days.
<csr-id-64ff0a77062d35add1a2dd422bb61075647d1a36/>
<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)649f588)beba720)37ba461)2e0ce50)9fa1054)
</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>
095c673)5755271)55f379b)f72ecce)
</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>add str::precompose_bstr() for convenience
str::precompose_bstr() for convenience<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
45b4470)f2e111f)f458966)a0deb06)91b1855)598d7a2)5fc379d)c5c69bd)3a5a229)fceed92)b40af1d)f26f298)face359)str::precompose_bstr() for convenience (9e3acde)
</details>add str::to_precomposed_unicode(), effective on apple devices only.
str::to_precomposed_unicode(), effective on apple devices only.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
eb6aa8f)6a2e0be)5d176fc)str::to_precomposed_unicode(), effective on apple devices only. (eace8bf)
</details>3 commits contributed to the release.
<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>4 commits contributed to the release.
<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>Add Buffers type. It allows to more easily manage a form of 'double buffering' to better manage conditional alteration of a source buffer, and to impl
Buffers type.
It allows to more easily manage a form of 'double buffering'
to better manage conditional alteration of a source buffer,
and to implement conversion pipelines which conditionally
transform an input over multiple steps.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
55d386a)d3dcbe5)dfb3f18)Buffers type. (86cdb42)c0e72fb)b65a80b)065ab57)
</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>
107a64e)16295b5)c4cc5f2)5cb3589)2fc66b5)9064ea3)
</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>
27e8c18)00f96fb)6fc7497)
</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>
ea9f942)18b0a37)aa16c8c)4f635fc)
</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>
9a9fa96)8f15cec)3ef5c90)9375cd7)facaaf6)
</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>
91134a1)30a1a71)f37a930)gix-utils is in early mode. (0f3b65f)
</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)8dbd0a6)7f06458)5d2b5d0)19338d9)gix-fs crate to consolidate all filesystem utilities (f8cc33c)23ee47f)3d47919)ef8f405)
</details>One column per quarter.