Releases: Byron/crates-index-diff-rs
v28.0.0
Bug Fixes (BREAKING)
- Upgrade to gix 0.72
Commit Statistics
- 1 commit contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- Upgrade to gix 0.72 (44c5806)
v27.0.0
New Features (BREAKING)
- upgrade gix to 0.71
Commit Statistics
- 2 commits contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
v26.0.0
New Features
- use github fast path to check for changes before git pull
Chore (BREAKING)
- upgrade gix to v0.67
Commit Statistics
- 4 commits contributed to the release.
- 107 days passed between releases.
- 2 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
v25.0.0
Upgrade gix
to 0.63 and crates-index to use the same version of gix
that contain security fixes.
Commit Statistics
- 2 commits contributed to the release.
- 85 days passed between releases.
- 0 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
v24.0.0
Chore (BREAKING)
- upgrade
gix
to v0.62
Commit Statistics
- 2 commits contributed to the release.
- 78 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
v23.0.0
Chore (BREAKING)
- upgrade
gix
to 0.58
Commit Statistics
- 1 commit contributed to the release.
- 29 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- Upgrade
gix
to 0.58 (7044076)
- Upgrade
v22.0.0
A maintenance release without any API changes. The major version bump is just to signal the change
of the gix
dependency to version v0.57.
Chore (BREAKING)
- update
gix
to v0.57
Commit Statistics
- 5 commits contributed to the release.
- 53 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
v21.1.0
Chore
- upgrade
gix
to 0.55.2
New Features
-
deterministic order if multiple changes are applied in one modification.
This can happen if a crate is yanked and unyanked in one commit, which happens
in practice even though I am not sure how it's possible.Related issue: rust-lang/docs.rs#2295
Other
- improve docs and be more clear about ordering.
Commit Statistics
- 5 commits contributed to the release.
- 41 days passed between releases.
- 3 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
v21.0.0
New Features (BREAKING)
-
upgrade to
gix
v0.54 (from v0.50)
This may produce smaller binaries.Further, no performance option is set anymore to leave this in the hands of
the final binary.
Commit Statistics
- 6 commits contributed to the release over the course of 83 calendar days.
- 83 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
v20.0.0
Chore
- uprgade
gix
tov0.48
Bug Fixes (BREAKING)
-
split
Change::Delete
intoChange::VersionDeleted
andChange::CrateDeleted
.
This resolves an ambiguity (facilitated by incorrect documentation) that would emit
Change::Delete
when a single version was deleted, even though downstream that would
rightfully be interpreted as deleting the whole crate.Adimittedly, previously there were no single-version deletions, just yanks, so we didn't
think of it either.
Commit Statistics
- 4 commits contributed to the release over the course of 10 calendar days.
- 11 days passed between releases.
- 2 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages