GitoxideLabs/gitoxide gitoxide-core-v0.61.0

gitoxide-core v0.61.0

on GitHub

New Features

• expose git notes in gix::Repository

  Add the notes feature and Repository::notes as the porcelain layer over gix-note
  for repeated queries and mutations.

  Select the default notes ref from core.notesRef, including the GIT_NOTES_REF
  environment override represented in config::tree, and fall back to
  refs/notes/commits. Discover additional display refs from notes.displayRef or
  GIT_NOTES_DISPLAY_REF, expand glob patterns, preserve display order, and avoid
  duplicates.

  For mutations, accept conventional short notes-ref names, write note blobs and
  notes commits, and update refs with compare-and-swap expectations so concurrent
  changes are not silently overwritten.

• use Git signature configuration in gix commit verify

  Replace the command-specific GPG invocation with gix::Commit::verify_signature
  so the CLI and library share one implementation and one interpretation of
  repository configuration.

  This extends the command from hard-coded OpenPGP verification to the OpenPGP,
  X.509, and SSH formats supported by Git, including configured programs and trust
  policy. Preserve verifier diagnostics on stderr and fail when a signature is
  invalid or insufficiently trusted.

  Enable the gix command feature in gitoxide-core to make the shared verification
  API available.

• support cloning a single revision

  A full object ID passed through with_ref_name() produced an object-ID refspec
  mapping and panicked while clone assumed every mapping had a name. Branch and
  tag checkout also retained ordinary clone tracking semantics instead of offering
  a single-revision mode.

  Add PrepareFetch::with_revision() and gix clone --revision for full refs, HEAD,
  and full object IDs. Revision clones use a one source-only implicit refspec,
  detach HEAD to the fetched commit, create no ordinary refs, persist no fetch
  refspec, and disable tag following. Existing with_ref_name() and --ref behavior
  stays unchanged.

  This follows Git commit 337855629f59 (builtin/clone: teach git-clone(1) the
  --revision= option) and its t/t5621-clone-revision.sh behavior.

Bug Fixes

• peel revspecs to a commit in gix merge-base
  The revspecs were resolved with rev_parse_single() and handed to the
  commit-only merge-base traversal unchanged, so a revspec naming an annotated
  tag arrived as the id of the tag object. No commit is found for such an id and
  no error is raised. In a clone of this repository,
  gix merge-base HEAD cargo-smart-release-v0.10.0 cargo-smart-release-v0.1.0
  printed 0fa37f5, dropping the tag and
  computing the base of the two revspecs that were left, while git merge-base
  with the same arguments prints ceb6dff - the
  commit the annotated tag points at. Git dereferences tags before computing
  anything.

  Each revspec is now peeled to a commit before the traversal. Lightweight tags,
  branches and raw commit ids resolve as before, and a revspec that cannot be
  peeled to a commit is rejected with the peel error.

Commit Statistics

• 26 commits contributed to the release over the course of 30 calendar days.
• 30 days passed between releases.
• 4 commits were understood as conventional.
• 1 unique issue was worked on: #1930

Commit Details