Similar to this discussion, I am running a CI/CD pipeline with separate build and deploy steps, with dist/ passed between them as an artifact. If I use poetry-dynamic-versioning, my build is correctly versioned as configured. However, as pointed out in the linked discussion, poetry publish only looks for builds of the current version to be published, and it's reading the 0.0.0 placeholder. This leads to
$ poetry publish
No files to publish. Run poetry build first or use the --build option.
despite my dynamically-versioned builds being present in dist/.
Similar to this discussion, I am running a CI/CD pipeline with separate build and deploy steps, with
dist/
passed between them as an artifact. If I usepoetry-dynamic-versioning
, my build is correctly versioned as configured. However, as pointed out in the linked discussion,poetry publish
only looks for builds of the current version to be published, and it's reading the0.0.0
placeholder. This leads todespite my dynamically-versioned builds being present in
dist/
.