fix(pdm): change pdm update strategy to eager #29183
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
huxuan
changed the title
huxuan
force-pushed
the
xuan.hu/pdm-update-strategy
branch
from
b9974df
to
3399bfd
Compare
huxuan
force-pushed
the
xuan.hu/pdm-update-strategy
branch
from
3399bfd
to
55fb916
Compare
viceice
reviewed
May 21, 2024
viceice
approved these changes
May 21, 2024
secustor
approved these changes
May 21, 2024
|
🎉 This PR is included in version 37.371.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Changes
Per discussion here, we should use
eagerupdate strategy when using pdm.Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: