use poetry-dynamic-versioning
, update workflows to consolidate steps
#2488
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Use the
poetry-dynamic-versioning
plugin to automatically set package version.This plugin automates the use of Dunamai (what is currently used).
What Changed
Added
runway.__version_tuple__
set bypoetry-dynamic-versioning
Changed
pipx
is now used instead ofpip
when installingpoetry
on the devcontainer imagepoetry-dynamic-versioning
is injected into the same venv aspoetry
actions/setup-python
,Gr1N/setup-poetry
, and a few script steps withfinleyfamily/action-setup-python
pull_request_target
into a single workflowrunway.__version__
is no longer determined at runtime. it is set bypoetry-dynamic-versioning
when building a releaserunway_version
is nowNone
instead of>=1.10
__version__
is statically set to0.0.0
outside of the build & publish workflowRemoved
version
target fromMakefile
as it is no longer needed