fix: remediate dependency vulnerabilities across npm, go, pip, and rubygems - #732
Open
devin-ai-integration[bot] wants to merge 1 commit into
Open
fix: remediate dependency vulnerabilities across npm, go, pip, and rubygems#732devin-ai-integration[bot] wants to merge 1 commit into
devin-ai-integration[bot] wants to merge 1 commit into
Conversation
…bygems Bump vulnerable direct and transitive dependencies flagged by Dependabot and Wiz. Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Contributor
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified FilesNo covered modified files...
|
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
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.
Summary
Automated dependency-vulnerability remediation for findings reported by GitHub Dependabot and Wiz. Only findings that are actionable under the severity/age policy (critical immediately; high/moderate after a 7-day hold; low ignored; must have a published fixed version) and that are still present in the manifests/lockfiles are included. Stale alerts (already patched in the lockfile, e.g.
next,vite,djangoinsdk/highlight-pyafter this change) were verified against the lockfiles rather than trusted blindly.Fixed:
github.com/gofiber/fiber/v2turbohonovalibot@remix-run/routermarkdown-ituuid@remix-run/node(e2e/react-native)ajv(e2e/react-native)yaml(e2e/react-native)django(sdk/highlight-py dev dep)django(e2e/python)pytest(e2e/tests)loguru(e2e/python)^0→^0.7.3activesupport(RN example Gemfiles)>= 6.1.7.5→>= 7.2.3.1Deferred, with reasons:
org.bouncycastle:bcprov-jdk18on1.77 → 1.80.2 (Wiz, CVE-2025-14813) insdk/@launchdarkly/flutter/.../android/build.gradleandsdk/@launchdarkly/react-native-ld-session-replay/android/build.gradle. It is a build-time-only transitive of thecom.android.tools.build:gradle8.7.2 buildscript classpath (not shipped in artifacts); the real fix is an AGP upgrade. No Android SDK and no Maven Central access in this environment, so the change could not be built or verified — left for a dedicated PR.@angular/*,apollo-server-core,extract-zip,image-size,react-router-dom.@nestjs/core10 → 11,svelte4 → 5,react-router6 → 7,@opentelemetry/core1.30 → 2.x,file-type20 → 21,fast-xml-parser4 → 5,ts-deepmerge2 → 8, transitivenanoid4 → 5 andmarkdown-it12 → 14.@hono/node-server1.19.15,js-yaml3.15.1/4.3.1,nanoid3.3.18, plus the newestimage-sizeadvisories.pytest9 ine2e/python—pytest-asyncio0.25.3 requirespytest <9, so that manifest stays on^8.2.0.e2e/dotnet4/cs/packages.config): already covered by open Dependabot PRs (Bump the nuget group with 4 updates #513, Bump the nuget group with 1 update #509, Bump the nuget group with 1 update #496) and nuget.org is not reachable here, so no duplicate change.webpack,body-parser,@babel/core,json,msgpack,sqlite3,flask,@tootallnate/once).Excluded because it did not build: none — but see the environment caveats below.
How did you test this change?
Dependency-only change, no runtime behavior change, so no screenshots or staging link apply.
yarn install+yarn dedupe --check— clean.yarn build:sdk— 20/20 tasks pass.yarn build— 49/53; onlyangular.io-example#buildfails, because font inlining needsfonts.googleapis.com, which is blocked in this sandbox.yarn lint— 49/49 pass.yarn test— 76/77 pass.@highlight-run/next#testfails because the test boots a Next app whose corepack step downloads yarn fromrepo.yarnpkg.com(blocked here).aws-lambda#buildneeds thesamCLI, which is not installed.yarn format-check— the only warnings are local build artifacts underlib/(not tracked); all changed manifests pass Prettier.go build ./...,go vet ./...,go mod verifypass insdk/highlight-goande2e/go-plugin.sdk/highlight-gotests pass except a pre-existinglog.TestParseConsoleMessagesfailure (reproduced on the unmodified module), ande2e/gohas a pre-existing duplicatemaininfiber.go/echo.go.sdk/highlight-pysuite passes on Django 5.2.17 (259 tests);e2e/testsinstalls and collects on pytest 9;e2e/pythonimports Django/loguru/Flask cleanly.Are there any deployment considerations?
No migrations or backfills. Notes for reviewers:
sdk/highlight-pymoves its dev dependency Django from 4.x to 5.2.17 (the advisories have no 4.x fix); the shipped package is unaffected and the Django integration tests pass.activesupport >= 7.2.3.1, which needs Ruby >= 3.1. The Gemfiles still declareruby ">= 2.6.10"; CI runners use modern Ruby, but this is worth a look if anyone builds those examples on an old Ruby.turbomoves 2.8.7 → 2.9.14. Noteyarn buildcannot parserrweb/turbo.json(missingextends) on either version in a fresh checkout of this branch's base, so the build was validated with that submodule file locally patched; the submodule itself is untouched by this PR.yarn.lock,poetry.lock,package-lock.json,go.sum) is expected from these bumps; the React Native lockfile was regenerated and reformatted back to the repo's tab indentation to keep the diff readable.Link to Devin session: https://app.devin.ai/sessions/142c0a5e060144ec97c9177f692e8cb9
Note
Overview
Bumps dependency versions and lockfiles across e2e, SDK, and root tooling to clear Dependabot/Wiz findings, without changing application logic.
Go:
github.com/gofiber/fiber/v22.52.13 → 2.52.14 insdk/highlight-go,e2e/go, ande2e/go-plugin(withgo.sumupdates).npm/yarn: Root
package.jsonraisesturboto 2.9.14 and adds/updates resolutions forhono,valibot,@remix-run/router,markdown-it, anduuid;yarn.lockfollows.e2e/react-nativeadds overrides for@remix-run/node,ajv@8, andyaml@1and refreshespackage-lock.json.Python:
django→ 5.2.17 ine2e/pythonandsdk/highlight-py(dev);e2e/pythonpinsloguruto ^0.7.3;e2e/testsupgradespytestto ^9 (lockfile includes pygments).Ruby: React Native example Gemfiles require
activesupport >= 7.2.3.1instead of the older minimum/exclusion pattern.Reviewed by Cursor Bugbot for commit 92b9ed3. Bugbot is set up for automated code reviews on this repo. Configure here.