Git-darcs

Latest version: v0.9.1

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

Scan your dependencies

Page 3 of 5

0.7.1

- disable ancestry-path in oneline log

0.7.0

ignoring merge-commits improves the results in two ways:

- on some repositories git-darcs gets caught-up in merge-commits, recording almost only merges (I am testing with 6 repos I ofter work with)
- in the problematic repos ignoring merges increases the amount of recorded patches by a order of magnitude
- in repos with almost linear history ignoring merges has no effect on the amount of patches found
- the history becomes more readable

0.6.1

- send documentation to pypi

0.6.0

- I found more correct way to linearize history. No more wrong `rmfile` or `move` in the wrong direction. But the new method skips more commits. There is always a downside. 🤘

0.5.0

- remove --no-merge, it can cause wrong result (better confusing, but not wrong)

0.4.0

- relax python versions to 3.8. 3.9 and 3.10

Page 3 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.