Repository navigation
security: vulnerability remediation - #203
Open
kernel-internal[bot] wants to merge 1 commit into
Open
kernel-internal[bot] wants to merge 1 commit into
kernel-internal[bot] wants to merge 1 commit into
Conversation
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.
Vulnerability Remediation
Fixed
Not Included
Note
Low Risk
Lockfile-only transitive dependency updates with no runtime or auth/data-path code changes; main effect is refreshed browser compatibility data used by tooling.
Overview
Security-focused lockfile refresh for the
browserslistdependency tree (GHSA-73wf-gq98-2v4g). No application source orpackage.jsonchanges—onlyyarn.lock.Resolved versions move
browserslistfrom 4.28.1 to 4.28.7, with matching bumps to its data/tooling deps:baseline-browser-mapping,caniuse-lite,electron-to-chromium,node-releases, andupdate-browserslist-db. These packages are typically pulled in transitively (e.g. via Jest/Babel tooling) and affect how supported browser targets are computed at build/test time.Reviewed by Cursor Bugbot for commit fa37f0f. Bugbot is set up for automated code reviews on this repo. Configure here.