Currently we are using poetry version 1.7.1 and we have a requirement to build and publish the artifacts by adding random suffix to the version. The version <1.2.3> is the version that will be passed from pyproject.toml and now i need the packages to be published to jfrog with the version 1.2.3- (random suffix in our case is the timestamp).

Is there a way to achieve this without actually changing the version from pyproject.toml file

Commands used to build and publish are- Poetry build Poetry publish

Note - We are not incrementing the version and for every build run we need a unique package to be published by adding timestamp and how to achieve this feature dynamically

I have tried using poetry version $version to bump the version i need but still it is not detecting the packages to get published

Currently we are using poetry version 1.7.1 and we have a requirement to build and publish the artifacts by adding random suffix to the version. The version <1.2.3> is the version that will be passed from pyproject.toml and now i need the packages to be published to jfrog with the version 1.2.3- (random suffix in our case is the timestamp).

Is there a way to achieve this without actually changing the version from pyproject.toml file

Commands used to build and publish are- Poetry build Poetry publish

Note - We are not incrementing the version and for every build run we need a unique package to be published by adding timestamp and how to achieve this feature dynamically

I have tried using poetry version $version to bump the version i need but still it is not detecting the packages to get published

• publish
• python-poetry

• Please provide enough code so others can better understand or reproduce the problem. – Community Bot Commented yesterday

1 Answer 1

Since Poetry 2.0 Poetry provides a --local-version parameter for poetry build. See https://python-poetry.org/docs/cli/#build