Bump poetry version from 1.8.3 to 1.8.5 #11107
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
056fe5b to
e9ef4b4
Compare
noorul
added a commit
to noorul/smoke-tests
that referenced
this pull request
Dec 12, 2024
This change is required for dependabot/dependabot-core#11107
e9ef4b4 to
08b92d2
Compare
|
I think for the smoke tests to pass we need to merge dependabot/smoke-tests#240 first. Or is there a way to test them together? |
Probably.
For testing purposes, you can point the smoke tests workflow file at a specific branch, but then you'll need to be sure that the final PR doesn't include that custom branch name. |
|
I've merged the smoke test bump: |
08b92d2 to
809fd17
Compare
jeffwidman
approved these changes
Dec 12, 2024
jeffwidman
added a commit
that referenced
this pull request
Dec 14, 2024
We grouped the Python PR's to avoid noise. However, what I've observed in practice is we (and our users) care more about staying up to date on the package managers and not so much if the internal libraries used in our helpers stay up to date. So by breaking the package managers themselves out as distinct groups, it allows us to quickly move forward on those, without getting blocked if there's a breaking change in a minor helper library. Here's an example of exactly this problem: * #11107 (comment)
jeffwidman
added a commit
that referenced
this pull request
Jan 3, 2025
We grouped the Python PR's to avoid noise. However, what I've observed in practice is we (and our users) care more about staying up to date on the package managers and not so much if the internal libraries used in our helpers stay up to date. So by breaking the package managers themselves out as distinct groups, it allows us to quickly move forward on those, without getting blocked if there's a breaking change in a minor helper library. Here's an example of exactly this problem: * #11107 (comment)
jeffwidman
added a commit
that referenced
this pull request
Jan 3, 2025
We grouped the Python PR's to avoid noise. However, what I've observed in practice is we (and our users) care more about staying up to date on the package managers and not so much if the internal libraries used in our helpers stay up to date. So by breaking the package managers themselves out as distinct groups, it allows us to quickly move forward on those, without getting blocked if there's a breaking change in a minor helper library. Here's an example of exactly this problem: * #11107 (comment)
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.
PR #11079 is failing because of grouping. Not sure grouping is mandatory.