Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented May 1, 2025

Overview

We don't need to cap these dependencies at this time. If we do, we should cap them in a constraints-dev.txt file like we do in the core repo, but we don't actually need a constraints file if we're not testing upstream.


This is an automatic backport of pull request #517 done by Mergify.

We don't need to cap these dependencies at this time.

Signed-off-by: Courtney Pacheco <[email protected]>
(cherry picked from commit 6456296)
@mergify mergify bot added release-branch one-approval dependencies Pull requests that update a dependency file labels May 1, 2025
@mergify mergify bot merged commit a9a69e9 into release-v0.10 May 1, 2025
9 checks passed
@mergify mergify bot removed the one-approval label May 1, 2025
@mergify mergify bot deleted the mergify/bp/release-v0.10/pr-517 branch May 1, 2025 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file release-branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants