Bump postcss and styled-components in /react-dashboard - #8
Bump postcss and styled-components in /react-dashboard#8dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [postcss](https://github.com/postcss/postcss) to 8.5.25 and updates ancestor dependency [styled-components](https://github.com/styled-components/styled-components). These dependencies need to be updated together. Updates `postcss` from 8.4.49 to 8.5.25 - [Release notes](https://github.com/postcss/postcss/releases) - [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md) - [Commits](postcss/postcss@8.4.49...8.5.25) Updates `styled-components` from 6.3.12 to 6.4.4 - [Release notes](https://github.com/styled-components/styled-components/releases) - [Commits](https://github.com/styled-components/styled-components/compare/styled-components@6.3.12...styled-components@6.4.4) --- updated-dependencies: - dependency-name: postcss dependency-version: 8.5.25 dependency-type: indirect - dependency-name: styled-components dependency-version: 6.4.4 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
| punycode "^2.1.0" | ||
|
|
||
| "vite@^4.2.0 || ^5.0.0 || ^6.0.0 || ^7.0.0", vite@^5.4.14: | ||
| vite@^5.4.14: |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 1541 lists a dependency (vite) with a known High severity vulnerability.
ℹ️ Why this matters
Affected versions of vite and vite-plus are vulnerable to Exposure of Sensitive Information to an Unauthorized Actor / Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). Vite's server.fs.deny blocklist—which protects sensitive files such as .env and certificate files from being served—can be bypassed on Windows using alternate path representations (NTFS Alternate Data Stream syntax like /.env::$DATA?raw, or 8.3 short filenames), allowing an attacker to read otherwise-denied files when the dev server is exposed to the network.
To resolve this comment:
Check if you expose the Vite dev server or vite-plus to the network by configuring a non-loopback address using the --host CLI flag on Windows.
- If you're affected, upgrade this dependency to at least version 6.4.3 at react-dashboard/yarn.lock.
- If you're not affected, comment
/fp we don't use this [condition]
💬 Ignore this finding
To ignore this, reply with:
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasons
Questions about this issue? Reach out to Product Security in #prodsec-tools.
You can view more details on this finding in the Semgrep AppSec Platform here.
Bumps postcss to 8.5.25 and updates ancestor dependency styled-components. These dependencies need to be updated together.
Updates
postcssfrom 8.4.49 to 8.5.25Release notes
Sourced from postcss's releases.
... (truncated)
Changelog
Sourced from postcss's changelog.
... (truncated)
Commits
08c989cRelease 8.5.25 version24f6814Fix 8.5.17 visitor regressionf2fa53fAdd supply chain security requirement to PostCSS plugin guide10edf0bfix: return empty array for empty string in list.split (#2121)0ebe8adRelease 8.5.24 version73218c6Update dependencies9a114f6Preserve the BOM when stringifying (#2119)9069261Fix types checkeb9e1feRelease 8.5.23 version9d19c78Update dependenciesMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for postcss since your current version.
Updates
styled-componentsfrom 6.3.12 to 6.4.4Release notes
Sourced from styled-components's releases.
... (truncated)
Commits
5f69a30Version Packages (6.x) (#5770)537ea42fix(types): cut type-instantiation cost for polymorphic styled components (#5...e066341Version Packagesf692ec2fix(types): permissive props for un-introspectable targets, plus as-target au...f9f6546Version Packages1794522fix: include changesets re-touched since the last prerelease [skip ci]0097cdbci: branch-scoped Version Packages PR titled20b88efix(types): accept wrapped component's ownastype when spreading props (#5...786cd8bfix: don't double-count changesets already posted in a prior prerelease0dd1325chore: adjust release scriptDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.