Poetry-dynamic-versioning

Latest version: v1.4.0

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

Scan your dependencies

Page 5 of 10

0.17.0

* Added:
* Option `tool.poetry-dynamic-versioning.substitution.folders`.

0.16.0

* Changed:
* Option `tool.poetry-dynamic-versioning.subversion.tag-dir` is now `tool.poetry-dynamic-versioning.tag-dir`.
* Added:
* Option `tool.poetry-dynamic-versioning.tag-branch`.
* Option `tool.poetry-dynamic-versioning.full-commit`.

poetry-dynamic-versioning-plugin: v0.1.0 (2022-04-28)

* Changed:
* The Poetry 1.2+ plugin now has a new name, `poetry-dynamic-versioning-plugin`,
and this is its first release as a separate package.

The import-hack-based pseudo-plugin will continue to be called `poetry-dynamic-versioning`.

0.15.0

* Changed:
* Internal improvements/refactoring to unify code base with `poetry-dynamic-versioning-plugin`,
which is released as a separate package. These changes should not affect
users of `poetry-dynamic-versioning`.

0.14.1

* Fixed:
* The plugin maintained its own copy of the default `pattern`, which meant that
it could fall behind the copy in Dunamai and lead to surprising behavior.
The plugin now automatically uses the latest default from Dunamai directly
when you do not customize it in the plugin settings.

0.14.0

* Changed:
* The build backend is now poetry-core.
([Contributed by fabaff](https://github.com/mtkennerly/poetry-dynamic-versioning/pull/63))
* The default list of `substitution.patterns` now handles `__version__`
when it has a type annotation.
([Draft by da2ce7](https://github.com/mtkennerly/poetry-dynamic-versioning/pull/64))
* Added:
* Option to bypass the version control system and set a hard-coded version
in an environment variable called `POETRY_DYNAMIC_VERSIONING_BYPASS`.
([Draft by jonringer](https://github.com/mtkennerly/poetry-dynamic-versioning/pull/69))
* `branch`, `branch_escaped`, and `timestamp` formatting variables.

0.13.1

* Fixed an oversight where the default version tag pattern would only find
tags with exactly three parts in the base (e.g., `v1.0.0` and `v1.2.3`).
This is now relaxed so that `v1`, `v1.2.3.4`, and so on are also recognized.

Page 5 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.