chore(deps): bump dify-plugin to 0.9.1 to fix requests alert#2320
Merged
Conversation
dify-plugin 0.8.0 pinned requests>=2.32.3,<2.33.dev0, which held requests below the 2.33.0 security patch (GHSA for .netrc credential leak). Upstream dify-plugin 0.9.1 now requires requests>=2.33.1, lifting the cap. - dify-plugin 0.8.0 -> 0.9.1 - requests 2.32.5 -> 2.34.2
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
2 participants
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.
Follow-up to #2303. The
requestsalert on the dify integration was a holdout there becausedify-plugin==0.8.0pinnedrequests>=2.32.3,<2.33.dev0, holding it below the 2.33.0 patch. Upstream dify-plugin 0.9.1 now requiresrequests>=2.33.1, so the cap is gone.dify-plugin0.8.0 → 0.9.1requests2.32.5 → 2.34.2 (≥ 2.33.0 patch)uv lock --checkpasses.Remaining medium/low alerts (all genuine upstream/no-patch holdouts)
Re-verified against latest upstream — none are fixable today:
postcss(root)next@16.2.9(latest) still vendors postcss 8.4.31http-proxy-middleware(root)webpack-dev-server@5.2.5(latest) still pins^2.0.9; dev-server onlyuuid(root)sockjs(webpack-dev-server, dev-only); v3/v5/v6bufadvisory N/A to itsv4()usagejs-yaml(root)gray-matter@4.0.3(latest) pins js-yaml^3; forcing v4 breaks docs buildesbuild(root)tsup@8.5.1(latest) pinsesbuild ^0.27.0; advisory is dev-server-on-Windows, not our bundling usediskcache×2,torch