A GitHub Action for installing and managing Poetry in Python project CI/CD workflows.
actions-poetry is a GitHub Action that installs and configures Poetry for Python projects within GitHub Actions workflows. It solves the problem of managing Python dependencies consistently across CI/CD pipelines by providing a standardized way to install Poetry with isolated dependencies using pipx. The action supports multiple Python versions, Poetry versions, and operating systems.
Python developers who use Poetry for dependency management and want to integrate it into their GitHub Actions CI/CD workflows. Teams looking to standardize their Python build environments across different platforms.
Developers choose actions-poetry because it simplifies Poetry installation in CI/CD, supports version matrix testing, enables efficient caching of virtual environments, and works across all major operating systems without requiring Docker containers.
GitHub Actions for Python projects using poetry
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically installs Poetry with pipx for isolated dependency management, eliminating manual setup steps as highlighted in the key features.
Works across Ubuntu, macOS, and Windows GitHub runners, enabling consistent CI/CD workflows for diverse development environments.
Supports matrix strategies for multiple Python and Poetry versions, allowing comprehensive testing across different configurations as shown in the workflow example.
Enables caching of virtual environments with GitHub Actions Cache to speed up dependency installation, though it requires manual configuration as detailed in the README.
Requires separate Python installation via actions/setup-python or similar, adding complexity to workflows compared to all-in-one solutions.
Needs manual setup of poetry.toml or command-line configurations for in-project virtual environments to enable effective caching, as admitted in the README.
Major version updates (v2 and v3) introduced breaking changes, such as switching from Docker to host runners and pipx installation, which can disrupt existing workflows.