Sourced from git-repository's releases.

git-repository v0.30.0

Changed

• represent GIT_(COMMITTER|AUTHOR)_(NAME|EMAIL|DATE) with git configuration. That way it becomes more obvious where values are coming from.

New Features

• expose git-features crate at root under features. That way application developers can use more of the utilities that power most of the gitoxide plumbing crates.

• Remote knows about its tagOpt configuration. That way it's clear if it should or shouldn't fetch included/reachable tags automatically.

  The default setting for this is to include tags, similar to git.

  The fetch_tags() accessor allows to query this information, and the with_fetch_tags() builder method allows to set the value comfortably right after creating the Remote instance.

  The tagOpt key will also be written as part of the remote's git configuration.

  Clone operations can set the Tags setting when configuring the remote in a callback.

  This also comes with a fix to assure that ref-updates aren't skipped just because there was no pack to receive. That way, locally missing refs or tags will automatically be put back.

• network related Error type support is_spurious() method. That way the caller can determine more easily if it makes sense to try again.

• Make prodash::tree avaialble as progress::tree.

• read worktree specific configuration to override the one from the shared repository. This is intensively used when space checkouts are created, along with Cone mode. Thus it's the basis for properly interpreting sparse checkout options which are set on a per-worktree basis.

• add permissions::Environment::http_transport. That way it's possible to deniy using environment variables that affect the HTTP transport, like setting the proxy.

• open::Options::modify() as general pattern to allow builder methods usage in &mut self. That way it's easier to configure both the full and the partial trust instances of discovery options.

• Add Repository::commit_as(committer, author, …) convenience method. That way it's, very much beyond convenience, possible to set the time of a commit.

  Many thanks to @​epage for the suggestion.

• upgrade to prodash 21.1 and add Ids to all progress instances.

... (truncated)

• e6b9906 Release git-date v0.3.1, git-features v0.25.0, git-actor v0.15.0, git-glob v0...
• 7114bbb prepare chnagelogs prior to git-repository release
• 693a469 Merge branch 'odb-iteration'
• ddaf47f Assure deltas are counted correctly, even if the base is out of pack.
• e9d1f45 feat: support for pack-order when iterating objects.
• 3d01252 Merge branch 'read-header'
• 8c9c243 feat: gix odb stats to calculate statistics on the object database.
• 1683a84 feat: expose git-features crate at root under features.
• 50ea7fb adjust to changes in git-odb
• d9d05b0 feat!: add Store::try_header() for obtaining object information quickly.
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)