Release v0.24.0

CHANGELOG.md

@@ -1,5 +1,9 @@
-## Unreleased
+## v0.24.0 (2023-06-30)
 
+* Added:
+  * `POETRY_DYNAMIC_VERSIONING_COMMANDS_NO_IO`
+    environment variable to prevent the plugin from modifying files during certain commands.
+    The plugin still sets the dynamic version in memory so that Poetry itself can write it as needed.
 * Changed:
   * During `poetry version`, the plugin still activates, but no longer modifies pyproject.toml.
 

README.md

@@ -275,6 +275,7 @@ you can apply some global overrides via environment variables.
   For example, `build,publish` will limit the dynamic versioning to those two commands.
 * `POETRY_DYNAMIC_VERSIONING_COMMANDS_NO_IO`:
   Comma-separated list of Poetry commands during which the plugin should **not** directly modify files.
+  The plugin will still set the dynamic version in memory so that Poetry itself can write it as needed.
   Default: `version`.
 
 ## Command line mode
@@ -296,7 +297,9 @@ Refer to [the Dunamai documentation](https://github.com/mtkennerly/dunamai#vcs-a
 All of [Dunamai's caveats](https://github.com/mtkennerly/dunamai#other-notes) apply.
 In addition to those:
 
-* The dynamic version is not available during `poetry run` or `poetry shell`.
+* The dynamic version is not available during `poetry run` or `poetry shell`
+  because of a [Poetry design choice](https://github.com/python-poetry/poetry/issues/8092)
+  that prevents the plugin from cleaning up after itself.
 * Regarding PEP 517 support:
 
   `pip wheel .` and `pip install .` will work with new enough Pip versions

pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "poetry-dynamic-versioning"
-version = "0.23.0"
+version = "0.24.0"
 description = "Plugin for Poetry to enable dynamic versioning based on VCS tags"
 license = "MIT"
 authors = ["Matthew T. Kennerly <mtkennerly@gmail.com>"]