Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

11.1.3 (2022-09-01)

Bug Fixes

• switch git2 back to v0.14 - v0.15 is a breaking change… …for everyone who uses git2 as direct dependency as well due to libgit2-sys.

Commit Statistics

• 1 commit contributed to the release.
• 1 commit was understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

11.1.2 (2022-09-01)

Bug Fixes

• make fetches work again by using safe-performance mode of git-repository. This fixes the 'zlib stream broken' issue when fetching crates.io changes which was caused by git-repository configuring for max-performance by default, which affects a crate used by git2 as well. For some reason, changing to zlib-ng as backend wasn't taken kindly by libgit2 causing it to fail after a short while of receiving a pack from the remote.

  The fix avoids making such modifications to the zlib crate, allowing both crates, git-repository and git2 to co-exist in the same dependency tree.

Commit Statistics

• 7 commits contributed to the release.
• 1 day passed between releases.
• 1 commit was understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

11.1.1 (2022-08-31)

Bug Fixes

• Consider all crates yanked if 'yanked = true'. Previously, due to a missing test, a bug snuck in that would assume that all lines in an added files must be new versions, marking them as Change::Added. This ignored the fact that any line could also carry a yanked crate, misrepresenting them.

  This is now fixed, and yanked crates generally show up as Change::Yanked.

  One might take this as a hint that diffentiating by yank status might not be that useful after all as it doesn't scale that well. Maybe a future version changes how Change is represented.

Commit Statistics

• 3 commits contributed to the release.
• 1 day passed between releases.
• 1 commit was understood as conventional.
• 1 unique issue was worked on: #19

Commit Details

11.1.0 (2022-08-30)

New Features

• make the name of the remote configurable. This is primarily used in testing and we try even harder to make it fail to deal with squashed remote references, but it seems to work fine.

  For good measure, now using + in the refspec to assure it forces an update.

Bug Fixes

• assure refs can be reet when fetching to support squashing. Previously tests didn't replicate this, now they do.

Commit Statistics

• 5 commits contributed to the release over the course of 1 calendar day.
• 1 day passed between releases.
• 2 commits were understood as conventional.
• 1 unique issue was worked on: #16

Commit Details

11.0.0 (2022-08-28)

Changed (BREAKING)

• Use gitoxide Repository instead of git2::Repository This comes with plenty of changes to the API of the last_seen_reference() and to the lower-level methods that take object ids (now git::hash::ObjectId.

  Note that git2 is still used internally for fetching and cloning. This change was made to assure that at no time there are two open repositories (once for git2, once for gitoxide), as this has the potential to double resource usage for file handles.

• move CloneOptions into index module. The index module is now public for that reason.

Commit Statistics

• 39 commits contributed to the release over the course of 1 calendar day.
• 97 days passed between releases.
• 2 commits were understood as conventional.
• 1 unique issue was worked on: #16

Thanks Clippy

Clippy helped 2 times to make code idiomatic.

Commit Details

10.0.0 (2022-05-23)

New Features (BREAKING)

• Add support for detecting deleted crates. Previously there was no need to do that as deletions couldn't happen - crates are yanked instead.

  Now that the ecosystem experienced its first (known) supply-chain attack crates can also be deleted and we should be able to detect that to allow downstream users to act on this automatically.

Bug Fixes

• update version in usage example

Commit Statistics

• 10 commits contributed to the release over the course of 84 calendar days.
• 85 days passed between releases.
• 2 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Thanks Clippy

Clippy helped 1 time to make code idiomatic.

Commit Details

9.0.0 (2022-02-26)

• Upgrade to git2 v0.14, a BREAKING change. In order to use this release, assure that other dependencies also use git2 v0.14.

Commit Statistics

• 7 commits contributed to the release.
• 12 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

8.0.1 (2022-02-14)

• Only download the master branch on clone, not all branches, to greatly reduce the initial download size from nearly 800MB to just about 100MB.

Commit Statistics

• 4 commits contributed to the release.
• 197 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v8.0.0 (2021-07-31)

• Add fetch-options to CloneOptions to allow private crate index repositories

Commit Statistics

• 6 commits contributed to the release.
• 429 days passed between releases.
• 0 commits were understood as conventional.
• 1 unique issue was worked on: #11

Commit Details

v7.1.2 (2020-05-28)

• Documentation update

Commit Statistics

• 2 commits contributed to the release over the course of 1 calendar day.
• 4 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v7.1.1 (2020-05-23)

• Make new feature from v7.1.0 actually usable

Commit Statistics

• 3 commits contributed to the release.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v7.1.0 (2020-05-23)

• Add Index::from_path_or_cloned_with_options(…) to allow cloning from different crates repositories.

Commit Statistics

• 5 commits contributed to the release over the course of 43 calendar days.
• 54 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v7.0.1 (2020-03-29)

• disable unused dependency in git2 for lower compile times

Commit Statistics

• 2 commits contributed to the release.
• 7 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v7.0.0 (2020-03-22)

• update dependencies and upgrade git2 to 0.13.0

Commit Statistics

• 1 commit contributed to the release.
• 16 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v6.2.0 (2020-03-06)

• Add support for setting the last seen reference directly. Useful in conjunction with peek_changes(…).

Commit Statistics

• 1 commit contributed to the release.
• 3 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v6.1.0 (2020-03-02)

• Add support for progress messages by adding the (fetch|peek)_changes_with_options(git2::FetchOptions) variants.

Commit Statistics

• 1 commit contributed to the release.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v6.0.0 (2020-03-02)

• Update to git2 v0.12.0

Commit Statistics

• 1 commit contributed to the release.
• 1 day passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v5.1.0 (2020-03-01)

• add peek_changes() method, which is like fetch_changes(), but doesn't remember which changes it already saw. Use indx.last_seen_reference().set_target(oid) to get a similar effect as if fetch_changes() had been called.

Commit Statistics

• 4 commits contributed to the release over the course of 10 calendar days.
• 10 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v5.0.5 (2020-02-19)

Commit Statistics

• 2 commits contributed to the release over the course of 13 calendar days.
• 13 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v5.0.4 (2020-02-05)

Commit Statistics

• 2 commits contributed to the release over the course of 2 calendar days.
• 2 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v5.0.3 (2020-02-03)

Commit Statistics

• 2 commits contributed to the release.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v5.0.2 (2020-02-02)

• speed up diff parsing - skip conversion to utf8

Commit Statistics

• 2 commits contributed to the release.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v5.0.1 (2020-02-02)

• expose the 'git2' crate - useful for error handling

Commit Statistics

• 4 commits contributed to the release over the course of 1 calendar day.
• 1 day passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v5.0.0 (2020-02-01)

• update to libgit 0.11
• provide all information known about the crates, similar to the crates-index crate

Commit Statistics

• 3 commits contributed to the release.
• 163 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v4.0.2 (2019-08-22)

• update dependencies

Commit Statistics

• 2 commits contributed to the release.
• 47 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v4.0.1 (2019-07-05)

Commit Statistics

• 2 commits contributed to the release.
• 474 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v4.0.0 (2018-03-17)

• switch from rustc-serialize to serde

Breaking Changes

• CrateVersion::from_crates_diff_json(...) was removed in favor of CrateVersion::from_str(...) which is powered by serde.

Commit Statistics

• 6 commits contributed to the release over the course of 4 calendar days.
• 441 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v3.0.0 (2016-12-30)

• use git2 v0.6 instead of v0.4 to support openssl-sys 0.9.

Chore

• use latest version of git2 That way, crates-io-cli can used the latest crates. Version two is used by doc.rs and must remain as is.

Commit Statistics

• 1 commit contributed to the release.
• 3 days passed between releases.
• 1 commit was understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v2.0.1 (2016-12-27)

Add a tutorial to the documentation.

Documentation

• add reference to usage example. We are using the crates-cli as an example, even though it certainly is not the cleanest one possible.

Commit Statistics

• 1 commit contributed to the release.
• 1 commit was understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v2.0.0 (2016-12-26)

Chore

• update to v2.0.0

Bug Fixes

• cargo: use git2 version for compat with docs.rs (0ceebed3)
  • use git2 version for compat with docs.rs Otherwise docs.rs cannot use use. This is due to the issue described here:

Commit Statistics

• 2 commits contributed to the release.
• 2 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v1.0.1 (2016-12-26)

Other

• crates.io badge [skip ci]

Bug Fixes

• makefile: make quick tests quick again (9aa756ae)
  • make quick tests quick again
• display: implementation for changetype (8ed9a81f)

New Features

• implementation for changetype
• v1.0.1

Commit Statistics

• 4 commits contributed to the release.
• 4 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

v1.0.0 (2016-12-26)

Chore

• v1.0.0
• be compatible with docs.rs See
• fix keywords
• see why makefile is not working
• found an illegal-instruction error Just run cargo test
• intermediate crate info from hunk However, it's not yet working
• first commit

Other

• docs for all remaining methods.
• documentation for crateversion
• customizations for us This could possibly work actually
• test osx as well
• allow to change seen-ref name
• show backtrace
• attempt of fetch_changes implementation It fails as it cannot create the correct reference.
• support for unyanking We just count it as adding a crate, which also makes sense.
• handle yanked files
• now seeing the first added crates
• automate running tests quickly Using an existing checkout is important enough to put it into a makefile for documentation and automation.
• support for commit'ishs for diffs
• first traversal method The test fails for the wrong reason though, as it fails to parse my refspec even though libgit2 seems to be able to do it properly, and a recent-enough version is used.
• test against all versions of rust
• simplify travis travis-cargo does nothing for us in this case.

New Features

• using openssl file as basis

Bug Fixes

• give up on osx Openssl can't be linked due to missing symbols, no matter what.

  Maybe ... the version is too new? Odd that it works locally though.

• see if openssl somehow works after all
• openssl setup from openssl-rs itself
• try the msvc 32bit version
• msys2 seems to be the problem here
• try to enforce linking latest openssl
• try disabling the cache Maybe that way, the 64 bit builds will work
• enforce more recent openssl lib Currently some symbols are missing or are named differently. Let's also see if it links it to the correct spot in /usr/local/opt/openssl
• only 1.1.0c seems to be working See
• remove 32 bit targets due to failure The previous version triggered this error: Error parsing appveyor.yml: Value can be either string or "secure" string. (Line: 5, Column: 7)
• attempt to set OPENSSL env vars
• try to allow 32 bit failures Could also remove them, but ideally it remains visible to maybe one day work.
• try without index-bare cache For now ... I have not seen it being cloned at all. Possibly the cache provides a none-empty directory ?
• custom code to get cmake onto osx
• let's hope it will actually run now
• set envvars propery
• remove debug prints
• remove error handling in makefile This isn't a good thing to do for all of those without cargo. However, let's see if it fixes the issue first.
• to work with GNU make
• finally the correct refspec Fair enough, need trees here after all!
• cmake binary installation
• use different cmake source
• cmake upgrade via before_script
• see if a custom source will get latest cmake
• enforce latest cmake

Refactor

• don't enforce branches Previously valid ref-names would be interpreted as branches, which limits their use despite the name indicating otherwise.

  Now every ref path is supported.

• use quick-error That way, the crate-error type is an actual error with all the relevant implementations.

  It's impossible to work without it, I think :).

• move crate into own module
• better diff.print implementation
• simplify fetch-changes error handling

• much nicer Crate from json It's good to know that we can chain everything, but that should only be done if there is an actual dependency of the respective values.

  Otherwise, just abort early.

• better error handling
• allow direct usage of objects as well

Test

• remove duplicate all crates are also iterated in the 'changedsincelast_fetch' test.
• fetch_changes() Just the frame and all testing I could think of
• assure we can handle the entire index
• first clone on demand Would be nice to be able to specify --depth as well.
• first failing test

Commit Statistics

• 61 commits contributed to the release over the course of 1 calendar day.
• 61 commits were understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details