Vcs-repo-mgr

Latest version: v4.2

Safety actively analyzes 625951 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 13

4.2

---------------------------

- Added this changelog.
- Added ``license`` key to setup script.

.. _Release 4.2: https://github.com/xolox/python-vcs-repo-mgr/compare/4.1.3...4.2

4.1.3

-----------------------------

Bug fix: Restore support for exporting to directories with relative pathnames.

.. _Release 4.1.3: https://github.com/xolox/python-vcs-repo-mgr/compare/4.1.2...4.1.3

4.1.2

-----------------------------

Bug fix: Make sure ``update_context()`` is called before ``is_bare()`` is invoked.

.. _Release 4.1.2: https://github.com/xolox/python-vcs-repo-mgr/compare/4.1.1...4.1.2

4.1.1

-----------------------------

Bug fix: Resolve issue `5`_ by expanding remote git branch names to be unambiguous.

.. _Release 4.1.1: https://github.com/xolox/python-vcs-repo-mgr/compare/4.1...4.1.1
.. _5: https://github.com/xolox/python-vcs-repo-mgr/issues/5

4.1

---------------------------

- Bug fix: Resolve issue `4`_ by implementing a new approach to "git branch
name discovery" (that works equally well for local branches as it does for
remote branches) by switching from ``git branch --list --verbose`` to ``git
for-each-ref``.

- Document MacOS compatibility, run MacOS tests on Travis CI. While I never
specifically intended for vcs-repo-mgr to be used on Apple systems, a
colleague of mine has been trying to do exactly this and has run into a
number of issues that are probably caused by platform incompatibilities in
vcs-repo-mgr and/or its dependencies.

.. _Release 4.1: https://github.com/xolox/python-vcs-repo-mgr/compare/4.0...4.1
.. _4: https://github.com/xolox/python-vcs-repo-mgr/issues/4

4.0

---------------------------

- Backwards incompatible: Force internal merge tool for Mercurial. After
isolating the test suite from ``$HOME`` my ``~/.hgrc`` was ignored and the
following setting disappeared:

.. code-block:: ini

[ui]
merge = internal:merge

Then I ran the `vcs-repo-mgr` test suite and ``meld`` popped up. Not what I
was expecting from an automated test suite! Although it seems unlikely to me
that someone would depend on the old behavior the introduction of ``hg
--config ui.merge=internal:merge`` is backwards incompatible and version
numbers are cheap, so I'm bumping the major version number :-).

I do think the new behavior is a better default for the Mercurial backend
given the focus of `vcs-repo-mgr` on automation, if only to make this backend
match the behavior of the other backends.

- Isolate the test suite from ``$HOME``. I recently added the following to my
``~/.gitconfig``:

.. code-block:: ini

[commit]
gpgsign = true

Then I ran the `vcs-repo-mgr` test suite and I was not amused :-P. This
should fix the underlying more generic issue.

.. _Release 4.0: https://github.com/xolox/python-vcs-repo-mgr/compare/3.0...4.0

Page 1 of 13

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.