chore: update lockfile - #203
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8aa6fce12a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| @@ -1,145 +1,142 @@ | |||
| # This file is automatically @generated by Poetry 2.4.1 and should not be changed by hand. | |||
| # This file is automatically @generated by Poetry 1.8.2 and should not be changed by hand. | |||
There was a problem hiding this comment.
When the cached Poetry installation in .github/workflows/pytest.yaml is Poetry 2.1.x, this Poetry 1.8.2-generated lockfile is rejected before the workflow reaches its tests. I verified with Poetry 2.1.4 that poetry check --lock—documented by its help as checking the lockfile against the current pyproject.toml—and poetry install --no-root both report that pyproject.toml changed significantly, while the parent lockfile passes the same check. Because the workflow caches an unpinned Poetry installation and runs poetry install, regenerate this lockfile with the currently supported Poetry version or pin the workflow to a version that accepts this content hash.
Useful? React with 👍 / 👎.
1 participant
No description provided.