Poetry install failing on github after poetry 1.4.1 release #450
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.
Changes Summary
Test branch to test the CI on github. This branch only contains a minor change to the README and serves to demonstrate that something is wrong with the poetry setup on the GitHub runners.
It also serves to mess around with the GH workflow file to fix the issue, without messing around on dev directly.
This bug could be related to pradyunsg/sphinx-theme-builder/issues/13. See also poetry #7691
UPDATE: I temporarily fixed this by pinning the poetry version to 1.4.0. The bug appeared with the release of poetry 1.4.1 on 2023/03/19. It may be that the real issue is a broken hash (that was not properly validated with poetry 1.4.0, but is now in 1.4.1). So the real culprit may be sphinx-theme-builder (see their issue 39), which introduces the broken hash leading to a
_WheelFileValidationError
intopydata_sphinx_theme-0.8.1-py3-none-any.whl
, which we have as a dependency. See also the issue 1253 of pydata-sphinx-theme.We will wait for an upstream fix, then remove the poetry version pinning.
Reviewer Checklist