chore: update poetry.lock using Poetry v1.1.15 #748
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Strange, the PR was merged but there's no commit in |
|
Indeed, the commit in the timeline event links to the "spelling fixes" one 🤔 |
|
It looks like the changes were applied though. |
|
It seems dependabot did your work in #749 and entered before this, so maybe git discarded it on merge for not having any new changes to add. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I've updated
poetry.lock(withpoetry lock --no-update, i.e. without resolving the dependencies) using Poetry v1.1.15 which sorts extras and extras dependencies, resulting in a more deterministic lock file and hopefully smaller diffs upon changes. In order to benefit from the improvement in Poetry v1.1.15, only Poetry v1.1.15+ should be used for updating dependencies from now on.