fix(airbyte-cdk): bump nltk and requests #48438
Closed
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
natikgadzhi
changed the title
aaronsteers
approved these changes
Nov 9, 2024
|
There are dependency issues in the CI. Is it related to those changes? |
wennergr
approved these changes
Nov 12, 2024
|
Working on nltk here: I think we can probably close this PR and move effort to the new one in the new repo. Over there, I'm still dealing with test failures (fwiw). |
|
@aldogonzalez8 and @aaronsteers did this in the new repo, closing this one. |
auto-merge was automatically disabled
November 20, 2024 18:47
Pull request was closed
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.
What
Bumps up the
nltkandrequestspackages in airbyte-cdk, fixes a few security vulnerabilities.Fixes #45121.
Fixes https://github.com/airbytehq/airbyte-internal-issues/issues/10490