Install Poetry using locked dependencies
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 1
Description
Problem to Solve
Installing Poetry with unlocked dependencies sometimes breaks due to regressions in dependencies.
Proposed Solution
Use a traditional pip-compile workflow to create a locked requirements.txt.
If inputs.poetry-version matches the default, use the lock file. Otherwise, use unlocked dependencies. I don't want to maintain multiple lock files for different versions of Poetry.
Use Renovate to keep the lock file up to date.
@mshafer-NI previously suggested using poetry export but I think that exports the dependencies for the current project, not for Poetry itself.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the reusable action's Poetry installation entry point and the definition of inputs.poetry-version. Check how dependency files and Renovate are configured. Done means the default Poetry version uses the locked requirements.txt, other versions use unlocked dependencies, and the lock file can be maintained by Renovate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100