Repository navigation
chore(deps): bump nltk from 3.9.4 to 3.10.0 - #381
Merged
Merged
Conversation
Bumps [nltk](https://github.com/nltk/nltk) from 3.9.4 to 3.10.0. - [Release notes](https://github.com/nltk/nltk/releases) - [Changelog](https://github.com/nltk/nltk/blob/develop/ChangeLog) - [Commits](nltk/nltk@3.9.4...v3.10.0) --- updated-dependencies: - dependency-name: nltk dependency-version: 3.10.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Replaces #360 (Dependabot security update).
Bumps
nltk3.9.4 -> 3.10.0 inuv.lock, resolving 5 open Dependabot alerts (#40, #39, #38, #37, #32).Why this PR instead of #360
main) and ignoretarget-branch: developin.github/dependabot.yml. Perdocs/release-process.mdthis repo uses git-flow, so dependency changes belong ondevelop..github/workflows/ci.ymlonly triggers ondevelop, so chore(deps): bump nltk from 3.9.4 to 3.10.0 #360 had no test coverage at all (onlylicense/cla).develop, GitHub Actions repeatedly failed to dispatch a check suite for its head commit (verified via/check-suites- nogithub-actionssuite created across three separate pushes). Re-cutting the identical change onto a fresh branch is the reliable way to get the full CI matrix to run.Risk assessment: low
nltkis a transitive dependency only (pulled in viaazure-ai-evaluation); it is absent frompyproject.tomland not imported anywhere insrc/. The bump addsdefusedxmlas a new transitive dependency, which is a hardened XML parser and is the security fix itself.The diff is byte-identical to #360, rebased onto current
develop.