EUREKA-883: Bump lodash 4.17.21 -> ^4.18.1 fix CVEs#3593
Merged
Conversation
julianladisch
requested review from
a team,
Artem-Akimov-EPAM,
exel711,
kdubniak,
kuzma-rezchenko-EPAM,
msinichenko,
vkapylou and
wafschneider
…26-2950 https://folio-org.atlassian.net/browse/EUREKA-883 Bump lodash from 4.17.21 to ^4.18.0 in resolutions section of package.json. This fixes * GHSA-xxjr-mmjv-4gpg CVE-2025-13465 - lodash prototype pollution * GHSA-f23m-r3pf-42rh CVE-2026-2950 - lodash Prototype Pollution
julianladisch
force-pushed
the
EUREKA-883-lodash
branch
from
f0d3d87 to
c100b45
Compare
julianladisch
changed the title
julianladisch
changed the title
ryandberger
previously approved these changes
Apr 30, 2026
zburke
previously approved these changes
Jun 15, 2026
`@folio/stripes-build` `1.1.0` includes `@folio/stripes-webpack` `6.1.0`, which omits a transitive dependency on `sharp` that relied on a post-install script. NPM lifecycle scripts were disabled in build infrastructure in folio-org/jenkins-pipeline-libs#162 to address FOLIO-4492.
`@folio/stripes-build` `1.1.1` updates `webpack` to `^5.104.1` to satisfy a feature requirement from `@folio/stripes-webpack` for STRWEB-144, details at folio-org/stripes-webpack#175. Yes, this change in the peer-deep requirements should have been labeled as a breaking change.
zburke
approved these changes
Jun 24, 2026
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
3 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.
4.17.21to^4.18.1inresolutionssection ofpackage.json. This fixes@folio/stripes-buildfrom1.0.0to1.1.1. This pulls in@folio/stripes-webpack6.1.0, which omits a transitive dependency onsharpthat relied on a post-install script. NPM lifecycle scripts were disabled in build infrastructure in run "yarn install" cautiously jenkins-pipeline-libs#162 to address FOLIO-4492.webpack^5.104.1to satisfy a feature requirement from@folio/stripes-webpackfor STRWEB-144, details at STRWEB-144 generate an asset manifest stripes-webpack#175. Yes, this change in the peer-deep requirements should have been labeled as a breaking change.