GitoxideLabs/gitoxide gix-v0.57.0

gix v0.57.0

on GitHub

Chore

• upgrade MSRV to v1.70
  Our MSRV follows the one of helix, which in turn follows Firefox.

New Features

• Repository::rev_parse*() now supports branch@{upstream|push|u|p}.
  Previously it would be parsed, but always error as the implementation didn't exist.
  Now it will return the fetch and push tracking branches respectively.

• Add Reference::remote_tracking_ref_name() and *::remote_ref_name().
  These methods mirror their respective Repository::branch_* prefixed versions.

• add Repository::branch_remote_tracking_ref_name().

• add push.default config key

• add config::Snapshot::trusted_program().
  That way it's possible to obtain an executable, program or script
  from a key in the configuration that is in a trusted section of the
  configuration.

  This goes along with a new command feature that brings in the command
  module at the top level to be able to execute such commands.

• add clone::PrepareFetch::with_in_memory_config_overrides().
  With it one can affect the repository configuration right before fetching.

New Features (BREAKING)

• Repository::remote_names|remote_default_name() now returns Cow<'_, BStr> instead of Cow<'_, str>.
  That way information won't degenerate due to enforcement of UTF-8.

Bug Fixes (BREAKING)

• rename Repository::branch_remote_ref() to Repository::branch_remote_ref_name(), add direction argument (also to Repository::branch_remote_name() and Repository::branch_remote()).
  This better differentiates the return value from the corresponding ref objects,
  which would require the named ref to exist in the repository.

  The direction argument allows to get the reference to push to as well.
  Further, it now takes a full ref name to support deriving the name of branches
  to push to.

  Regarding Repository::branch_remote(), previously, this functionality
  was only available from a Reference,
  but now it's more generally available with just a branch name.

  The method was also adjusted to permit looking up non-symbolic remote
  names, like remotes that are specified by their URL.

• mark gix::interrupt::init_handler() as unsafe
  The passed interrupt() argument will be called from a signal
  handler, so that needs to be documented and the call sites need to
  state that they fulfill the contract.

  Thanks to @Manishearth for pointing this out.

Commit Statistics

• 40 commits contributed to the release over the course of 22 calendar days.
• 22 days passed between releases.
• 10 commits were understood as conventional.
• 4 unique issues were worked on: #1158, #1165, #1178, #1191

Thanks Clippy

Clippy helped 1 time to make code idiomatic.

Commit Details