Releases: Byron/gitoxide
gix-pathspec v0.7.5
Bug Fixes
- assure empty paths are always matching a
Search
This improvement was triggered by this question.
Commit Statistics
- 6 commits contributed to the release over the course of 33 calendar days.
- 33 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-pack v0.51.0
Bug Fixes (BREAKING)
-
don't panic when unknown entry types are encountered.
Related to helix-editor/helix#10660
which runs into object types that are unknown.I have looked into this and couldn't find evidence of a new pack-entry type
in the Git codebase.It also looks like that Git will never write packs that aren't V2
- initially I thought it might write V3 based on some other criteria.
Commit Statistics
- 4 commits contributed to the release over the course of 9 calendar days.
- 38 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-odb v0.61.0
Bug Fixes
-
more robustness in the face of a trampling-herd of threads loading a single index.
The motivating example is here: praetorian-inc/noseyparker#179Previously, it was possible for a trampling herd of threads to consolidate the
disk state. Most of them would be 'needs-init' threads which could notice that
the initialization already happened, and just use that.But a thread might be late for the party and somehow manages to not get any
newly loaded index, and thus tries to consolidate with what's on disk again.
Then it would again determine no change, and return nothing, causing the caller
to abort and not find objects it should find because it wouldn't see the index
that it should have seen.The reason the thread got into this mess is that the 'is-load-ongoing' flagging
was racy itself, so it would not wait for ongoing loads and just conclude nothing
happened. An extra delay (by yielding) now assures it either seees the loading state
and waits for it, sees the newly loaded indices.Note that this issue can be reproduced with:
'./target/release/gix -r repo-with-one-pack -t10 --trace odb stats --extra-header-lookup' -
use
tempfilepermissions support to set the correct mode on unix.
Previousoly it would make an additional syscall to change permissions, which
is slower than necessary.
Commit Statistics
- 6 commits contributed to the release over the course of 10 calendar days.
- 38 days passed between releases.
- 2 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- Adjust changelogs prior to release (9511416)
- Release gix-date v0.8.6 (d3588ca)
- Merge branch 'status' (04ef31e)
- Adapt to changes in
gix-pack(bad5b48) - More robustness in the face of a trampling-herd of threads loading a single index. (addf446)
- Use
tempfilepermissions support to set the correct mode on unix. (7b3dc92)
gix-object v0.42.2
A maintenance release without user-facing changes.
Commit Statistics
- 2 commits contributed to the release over the course of 8 calendar days.
- 65 days passed between releases.
- 0 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-negotiate v0.13.1
A maintenance release without user-facing changes.
Commit Statistics
- 5 commits contributed to the release over the course of 8 calendar days.
- 68 days passed between releases.
- 0 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-mailmap v0.23.1
A maintenance release without user-facing changes.
Commit Statistics
- 2 commits contributed to the release over the course of 8 calendar days.
- 68 days passed between releases.
- 0 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-macros v0.1.5
A maintenance release without user-facing changes.
Commit Statistics
- 3 commits contributed to the release over the course of 8 calendar days.
- 68 days passed between releases.
- 0 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
gix-lock v14.0.0
A maintenance release without user-facing changes.
Commit Statistics
- 1 commit contributed to the release.
- 68 days passed between releases.
- 0 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- Adjust changelogs prior to release (9511416)
gix-index v0.33.0
New Features
- add
From<gix_object::tree::Mode> for gix_index::entry::Mode.
Other
- make clear that indices can contain invalid or dangerous paths.
It's probably best not to try to protect against violations of constraints
in this free-to-mutate data-structure and instead suggest to validate entry
paths before using them on disk (or use thegix_worktree::Stack).
Bug Fixes (BREAKING)
State::from_tree()now performs name validation.
Previously, malicious trees could be used to create a index with
invalid names, which is one step closer to actually abusing it.
Commit Statistics
- 8 commits contributed to the release over the course of 33 calendar days.
- 33 days passed between releases.
- 3 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- Adjust changelogs prior to release (9511416)
- Merge branch 'various-fixes' (d6cd449)
- Merge pull request from GHSA-7w47-3wg8-547c (79dce79)
State::from_tree()now performs name validation. (2ea87f0)- Apply suggestions from code review (bad9a79)
- Make clear that indices can contain invalid or dangerous paths. (b6a67d7)
- Add
From<gix_object::tree::Mode> for gix_index::entry::Mode. (9564699) - Merge branch 'cargo-fixes' (977346e)
gix-fs v0.11.0
Bug Fixes
- multi-process safe parallel filesystem capabilities probing
This is achieved by making filenames unique so they won't clash. - default to creating file-symlinks if it is dangling on Windows
This behaviour is the same as in Git.
Bug Fixes (BREAKING)
-
validate all components pushed onto the stack when creating leading paths.
This way, everyone using the stack with the purpose of
altering the working tree will run additional checks to prevent callers
from sneaking in forbidden paths.Note that these checks don't run otherwise, so one has to be careful
to not forget to run these checks whenever needed.
Commit Statistics
- 14 commits contributed to the release over the course of 8 calendar days.
- 38 days passed between releases.
- 3 commits were understood as conventional.
- 2 unique issues were worked on: #1354, #1373
Commit Details
view details
- #1354
- Default to creating file-symlinks if it is dangling on Windows (31d02a8)
- #1373
- Multi-process safe parallel filesystem capabilities probing (bec648d)
- Uncategorized
- Adjust changelogs prior to release (9511416)
- Merge branch 'various-fixes' (d6cd449)
- Merge pull request from GHSA-7w47-3wg8-547c (79dce79)
- Apply suggestions from code review (1242151)
- Adapt to changes in
gix-index(5f86e6b) - Apply suggestions from code review (ccbc119)
- Address review comments (fcc3b69)
- Apply suggestions from code review (bad9a79)
- Validate all components pushed onto the stack when creating leading paths. (874cfd6)
- Add validation for path components and tree-names (0d78db2)
- Merge branch 'status' (04ef31e)
- Improve the symlink probing by simplifying it (7a3c583)