Tags: vcs-python/libvcs
Tags
Tag v0.45.1 why: Ship the pytest plugin collection-ignore fix, which aborts collection for downstream suites that build docs before running tests, plus the runnable-doctest documentation pass. what: - Bump version to 0.45.1 in pyproject.toml, __about__.py, and uv.lock - Date the 0.45.1 CHANGES entry below the 0.46.x unreleased block - Promote the #544 fix from a bullet to a titled deliverable
Tag v0.45.0 why: Release 0.45.0 with the URL-registry and pytest-fixture isolation fixes plus the opt-in parallel test mode. what: - Bump version to 0.45.0 in pyproject.toml, __about__.py, and uv.lock - Date the 0.45.0 CHANGES entry and open a 0.46.x unreleased block
Tag v0.44.0 - verbatim command output by default Command output is now returned verbatim by default. `.run()` on the Git, Mercurial, and Subversion command classes returns exactly what the VCS printed, so a captured `git diff` re-applies with `git apply` and blob reads are byte-identical; the previous per-line trimming corrupted whitespace-significant output. This is a breaking change -- callers that want a bare value (a lone SHA, a branch name) pass the new `trim=True`. Downstream tools such as vcspull are unaffected, as they strip defensively. See CHANGES for the full release notes.
Tag v0.43.0 - pytest 9.1 compatibility The pytest plugin imports cleanly under pytest 9.1, which turned marks applied to fixture functions into a hard error. Because libvcs ships the plugin so it auto-loads when pytest runs, the previous release aborted the test session for any project that had libvcs installed and upgraded to pytest 9.1+; that no longer happens. Git, Mercurial, and Subversion fixtures now skip rather than error when their binary is unavailable. See CHANGES for the full release notes.
Tag v0.42.0 - GitSync clone depth GitSync gains a `depth` keyword argument so callers can clone at an arbitrary shallow depth (`git clone --depth N`), not just a single commit. Passing `git_shallow` or `tls_verify` to the GitSync constructor now sets the attribute instead of raising AttributeError on the next sync (a regression dating back to v0.4.4). See CHANGES for the full release notes.
PreviousNext
