Skip to content

chore(deps): update baseline-browser-mapping - #121034

Open
github-actions[bot] wants to merge 1 commit into
masterfrom
chore/update-baseline
Open

chore(deps): update baseline-browser-mapping#121034
github-actions[bot] wants to merge 1 commit into
masterfrom
chore/update-baseline

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

automated update of baseline-browser-mapping to suppress stale-data console warnings

Comment thread pnpm-lock.yaml

react-grid-layout@1.5.3:
resolution: {integrity: sha512-KaG6IbjD6fYhagUtIvOzhftXG+ViKZjCjADe86X1KHl7C/dsBN2z0mi14nbvZKTkp0RKiil9RPcJBgq3LnoA8g==}
deprecated: 'Ships stray files that were never in the repo: an ip_fetcher binary and its curl-sample source (1.5.0-1.5.3), plus a yarn-error.log containing local paths (1.5.3). Upgrade to 1.5.4, which is byte-identical apart from removing them. See https://github.com/react-grid-layout/react-grid-layout/issues/2269'

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The react-grid-layout dependency is pinned to version 1.5.3, which is deprecated for shipping stray files, including a binary and a log with local paths.
Severity: MEDIUM

Suggested Fix

Update the react-grid-layout dependency in package.json from version 1.5.3 to 1.5.4. The new version is byte-identical apart from removing the problematic files. After updating package.json, regenerate the lock file.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: pnpm-lock.yaml#L7845

Potential issue: The `pnpm-lock.yaml` file contains a deprecation warning for
`react-grid-layout@1.5.3`, indicating that this version ships with stray files: an
`ip_fetcher` binary and a `yarn-error.log` containing local paths. The project's
`package.json` explicitly pins this vulnerable version. While the pull request updated
the lock file, it missed the opportunity to resolve this known supply-chain security
issue by upgrading the package. Leaving this dependency unpatched introduces a security
and privacy risk, as unexpected files are present in the dependency tree.

Did we get this right? 👍 / 👎 to inform future reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants