Releases: mtkennerly/poetry-dynamic-versioning
Releases · mtkennerly/poetry-dynamic-versioning
v1.0.0b1 (2022-03-10)
- Changed:
- Implemented the official Poetry plugin interface.
v0.14.0 (2022-03-09)
- Changed:
- The build backend is now poetry-core. (Contributed by fabaff)
- The default list of
substitution.patterns
now handles__version__
when it has a type annotation. (Draft by da2ce7)
- 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) branch
,branch_escaped
, andtimestamp
formatting variables.
- Option to bypass the version control system and set a hard-coded version in an environment variable called
v0.13.1 (2021-08-09)
- 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
andv1.2.3
). This is now relaxed so thatv1
,v1.2.3.4
, and so on are also recognized.
v0.13.0 (2021-05-26)
- Changed:
- Broadened version range of Jinja2 dependency to support projects that need a newer version.
- Bumped the minimum Poetry version to 1.1.0, since the above Jinja2 change seemed to trip up Poetry 1.0.10 (on Python 3.7 and 3.8, but not 3.5 or 3.6, for some reason).
- Fixed:
- The plugin did not work on Fedora inside of Pip's isolated build environment, because the plugin would be loaded before some of its dependencies. Now, those imports are delayed until needed.
v0.12.7 (2021-05-20)
- Fixed:
- Parsing files containing special UTF-8 characters would result in an error. Files are now assumed to be UTF-8. (Contributed by rhorenov)
v0.12.6 (2021-04-19)
- Fixed:
- The previous
bump
fix only applied toformat-jinja
. It has now been fixed for other scenarios as well.
- The previous
v0.12.5 (2021-04-18)
- Fixed:
- When the
bump
option was enabled, the version would be bumped even when on a commit with a version tag. Now, no bumping occurs when on such a commit.
- When the
v0.12.4 (2021-03-05)
- Fixed:
- An incompatibility with
tox-poetry-installer
where the working directory
was received as astr
instead of aPath
.
(Contributed by cburgess)
- An incompatibility with
v0.12.3 (2021-02-19)
- Fixed:
-
Previously, when building a source distribution with
poetry build
, the plugin's config section would retain theenable = true
setting, which would then cause an error when installing the artifact since the VCS info would not be available. (This was not an issue for wheels generated bypoetry build
.)The dynamic version from build time is still present in the source distribution, so there is no need for the plugin at install time. Therefore, the plugin now temporarily sets
enable = false
so that that value will be placed in the source distribution, then restores the original setting for development purposes.
-
v0.12.2 (2021-01-30)
- Fixed:
- Another possible exception when applying patches if only
poetry-core
was installed and not the Poetry tool, particularly combined with Tox.
- Another possible exception when applying patches if only