π¨ [security] Update postcss 8.4.21 β 8.5.4 (minor) #165
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.
Welcome to Depfu π
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
π¨ Your current dependencies have known security vulnerabilities π¨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
β³οΈ postcss (8.4.21 β 8.5.4) Β· Repo Β· Changelog
Security Advisories π¨
π¨ PostCSS line return parsing error
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by 21 commits:
Release 3.3.11 versionFix CIFix RN supportMove to manually ESM/CJS dual packageRelease 3.3.10 versionFix Expo supportRelease 3.3.9 versionRemove dev file from npm packageRelease 3.3.8 versionUpdate size limitFix pool pollution, infinite loop (#510)Release 3.3.7 versionUpdate dual-publishRemove benchmark from CI for v3Fix CI for v3Move to pnpm 8Release 3.3.6 versionRelease 3.3.5 versionBackport funding optionUpdate dependenciesUpdate IE polyfill to fix last improve with reduce (#362)Release Notes
1.1.1
1.1.0
1.0.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
picocolors@1.1.1Add chalk v5 and yoctocolors to benchmarks (#88)Rework color detection (#87)fix: usage of `node12` in `testing.yaml` (#73)Use mitata, esbuild for benchmarking speed and size (#86)fix(types): move types declaration into "real" types declaration file (.d.ts) (#82)picocolors@1.1.0test: add test (shouldn't overflow when coloring already colored large text) (#74)feat: bright colors variants (#55)miscv1.0.1fix: iteratively replace "close" to avoid maximum stack error (#64)Fix color detection in edge runtime (#56)uniform api usage in complex benchmarkupdate benchmarks per recent job runCreate .gitignore (#37)Release Notes
1.2.1
1.2.0
1.1.0
1.0.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
1.2.1Update changelogImprove ts declarations (#27)Ensure null source is respected. (#26)Fix TS2306 βnot a moduleβ errors in type definitions (#16)1.2.0Update changelogFix typoAdd generator options to fromSourceMap (#22)1.1.0Add ignoreInvalidMapping option (#21)Do not throw an error since broken prev map is popular issue (#20)Update CHANGELOG.md1.0.3Update changelogUse sourceContents when non-null, even if it's an empty string (#17)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands