py(deps) libvcs 0.43.0 -> 0.44.0#556
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #556 +/- ##
=======================================
Coverage 83.85% 83.85%
=======================================
Files 30 30
Lines 4354 4354
Branches 873 873
=======================================
Hits 3651 3651
Misses 467 467
Partials 236 236 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
8 tasks
tony
added a commit
to vcs-python/libvcs
that referenced
this pull request
Jun 21, 2026
Command output is now returned exactly as the VCS printed it. The
runner used to strip every captured line, drop blank lines, and
remove the trailing newline, which corrupted whitespace-significant
output: a captured `git diff` was rejected by `git apply`,
`git cat-file blob` lost indentation and blank lines, and multi-line
errors were concatenated into one run-on line. Output is now
verbatim, with a `trim=True` opt-in for convenient bare-value reads.
Breaking changes:
`.run()` on the Git/Hg/Svn command classes (and the internal runner)
now returns output verbatim instead of trimmed -- the trailing
newline is kept. Pass `trim=True` for the previous bare-value
behavior:
Before: git.run(["rev-parse", "HEAD"])
After: git.run(["rev-parse", "HEAD"], trim=True)
High-level helpers are unaffected: GitSync.get_revision() still
returns a bare revision, and downstream vcspull (which strips
defensively) passes unchanged.
Also in this change:
- trim is forwarded from the git/hg/svn command methods, so the
opt-in works everywhere, not only the low-level runner.
- Multi-line stderr keeps its line breaks in CommandError.output,
instead of being concatenated into one run-on line.
- rev_list honors its date-range filters (since/until/after/before/
max_age/min_age), which were silently dropped.
- ADR 0001 records the decision, measured alternatives, and prior
art; a changelog entry summarizes the breaking change.
Companion PR: vcs-python/vcspull#556 -- validates the verbatim
default downstream; its suite passes unchanged.
tony
force-pushed
the
subprocess-trimming
branch
from
969ecea to
5c8b285
Compare
tony
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Raise the libvcs floor to v0.44.0 (PyPI release).
libvcs 0.44.0 returns VCS command output verbatim instead of trimming each line. That change lives at libvcs's low-level
.run()API; vcspull syncs through the high-level helpers (GitSync/HgSync/SvnSync), which are unaffected — so there are no vcspull code, configuration, or CLI changes.See libvcs CHANGES: https://libvcs.git-pull.com/history.html#libvcs-0-44-0-2026-06-21
Test plan
uv run pytest— full suite passes (1087 passed, 27 snapshots)uv run mypy— cleanuv run ruff check .— cleanuv run ruff format --check .— clean