Fix diff-poetry-lock check

Open
#119 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
build-system, tooling

Research direction

Start with the linked GitHub Actions failure and the diff-poetry-lock check, then inspect how the check invokes Poetry and which runtime dependency it assumes. Compare that behavior with the Poetry 2.0 release; done means the check runs successfully without an unchanged-file failure under the supported Poetry version.

Written by the indexing model from the issue text.

Description

diff-poetry-lock check broke without change so there must be a runtime dependency on something. Looking at this failure, it looks like it's using Poetry and perhaps the Poetry 2.0 release broke an assumption.

Dominant language
Makefile
Stars
31
Forks
6
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from target/make-python-devex

All issues in target/make-python-devex

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.