feat: fix security issues (PROVCON-5452)#2935
Open
darekplawecki wants to merge 3 commits into
Open
Conversation
✅ Deploy Preview for stoplight-elements ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for stoplight-elements-demo ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
darekplawecki
changed the title
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.
webpack5.50.0 → 5.76.0 — fixes knownwebpacksecurity advisory. Bothwebpack@5.50.0andwebpack@5.76.0selectors now resolve to 5.76.0.loader-utils2.0.0 → 2.0.3 — remediates prototype-pollution / ReDoS advisories. Only the exact-pinnedloader-utils@2.0.0was affected (^2.0.0 already resolved to 2.0.4).js-cookie2.2.1 → 3.0.7 (major) — only consumer is react-use'suseCookie, which uses get/set/remove via the default import; all unchanged in v3. v3 breaking changes (dropped IE support, removedwithConverter, ESM exports field) don't affect this usage, anduseCookieisn't invoked by Elements at runtime. Verified safe.ip-address9.0.5 → 10.1.1 (major) — only consumer is socks (proxy/dev tooling), which usesAddress4,Address6,Address6.fromByteArray, and.canonicalForm()— all present in v10. v10 still ships CommonJS (socks'srequire("ip-address")works) with engines.node >= 12; the v10 breaking change is internal (dropped jsbn for native BigInt). Verified safe.Note:
js-cookie3.0.6+ raised engine to node >=20, so I upgraded node version in the pipeline. Tested all workflows and it looks fine