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

view details

• Uncategorized
  • Merge branch 'gix-upgrade' (9bf5d93)
  • Upgrade gix to v0.62 (6377d3d)

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)

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

view details

• Uncategorized
  • Prepare changelog prior to release (98f24fe)
  • Merge branch 'maintenance' (2170563)
  • Turns out that using the resource cache is too costly (ad50624)
  • Remove git-lfs (2206723)
  • Update gix to v0.57 (bc3a8a2)

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

view details

• Uncategorized
  • Merge branch 'improvements' (28f0d1f)
  • Upgrade gix to 0.55.2 (e8b2c90)
  • Deterministic order if multiple changes are applied in one modification. (c404f67)
  • Assure gix versions are synced in the entire tree. (8576bc7)
  • Improve docs and be more clear about ordering. (7957987)

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

• Uncategorized
  • Upgrade to gix v0.54 (from v0.50) (34d3510)
  • Merge branch 'uprade-crates-index' (922e962)
  • Upgrade to latest version of crates-index to remove git2 (fa1b21c)
  • Merge branch 'test-version-delete' (e200a56)
  • Add a test specifically for the VersionDeleted variant. (959c566)
  • Refactor (b0f84d0)

v20.0.0

Chore

• uprgade gix to v0.48

Bug Fixes (BREAKING)

• split Change::Delete into Change::VersionDeleted and Change::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

Commit Details

view details

• Uncategorized
  • Split Change::Delete into Change::VersionDeleted and Change::CrateDeleted. (2c59dd4)
  • Uprgade gix to v0.48 (9946196)
  • Split VersionDeleted from crate-deletes (2caf814)
  • Fix stress-test invocation (967836b)

v19.0.0

Chore (BREAKING)

• upgrade to gix v0.47 (from v0.45).
  This includes integration with gix negotiation algorithms and support for
  multi-round negotiation just like git does it.

Commit Statistics

• 2 commits contributed to the release over the course of 13 calendar days.
• 13 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 to gix v0.47 (from v0.45). (f726287)
  • Try to fix the baseline test which now starts failing on CI (892561a)

v18.0.0

Chore (BREAKING)

• upgrade dependencies
  • gix 0.44 -> 0.45
  • hashbrown 0.13 -> 0.14

Commit Statistics

• 1 commit contributed to the release.
• 25 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 dependencies (7427603)

v17.0.0

Chore (BREAKING)

• upgrade gix from v0.37 to v0.44.
  Note that there is no breaking change, but the major version bump is merely
  for safety and to make it easy to reatain a certain gix version within the tree.

Commit Statistics

• 3 commits contributed to the release.
• 82 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 from v0.37 to v0.44. (b00ca99)
  • Reduce code-size by reusing the same type for Progress. (c3d5518)
  • Upgrade gix dependency to 0.44.1 (4489ef7)

v16.0.1

Bug Fixes

• make DependencyKind publicly accessible
  Previously it was used as field within an exported type, but it couldn't
  be used directly.

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
  • make DependencyKind publicly accessible (8d7b7b6)