Dunamai

Latest version: v1.21.1

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

Scan your dependencies

Page 1 of 9

1.21.1

* Fixed: Distance was calculated inconsistently for Git
when there were some tags and none matched the version pattern.

1.21.0

* Generally, when Dunamai can detect the VCS in use, but there's no version set yet,
then Dunamai uses 0.0.0 as a fallback, unless strict mode is enabled.
This is useful for new projects that do not yet have a release.

However, if there were some tags and none matched the version pattern,
then Dunamai would yield an error.
That wouldn't be helpful for a new project with some non-version tag,
and it could be incorrect for a monorepo with different tags for different packages.

Now, Dunamai will use 0.0.0 in this case as well, unless strict mode is enabled.
* You can now specify a pattern prefix.
For example, `--pattern default --pattern-prefix some-package-`
would match tags like `some-package-v1.2.3`.
This is useful if you just want a custom prefix without writing a whole pattern.
* Added `--ignore-untracked` option to control checking whether the repository is dirty.

1.20.0

* Updated `Version.bump()` to add a `smart` argument,
which only bumps when `distance != 0`.
This will also make `Version.serialize()` use pre-release formatting automatically,
like calling `Version.serialize(bump=True)`.

1.19.2

* Fixed an exception when a Git repository had a broken ref.
Git would print a warning that Dunamai failed to parse.

1.19.1

* Relaxed Python bounds from `^3.5` to `>=3.5` since Python does not follow Semantic Versioning.
* Fixed some `git log` commands that did not include `-c log.showsignature=false`.
([Contributed by pdecat](https://github.com/mtkennerly/dunamai/pull/75))

1.19.0

* Added a `--path` option to inspect a directory other than the current one.
The `Version.from_*` methods now also take a `path` argument.

Page 1 of 9

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.