Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: pgrade autoprefixer from 10.4.19 to 10.4.20 [Snyk] #397

Merged
merged 2 commits into from
Oct 28, 2024

Conversation

dhcrees
Copy link
Contributor

@dhcrees dhcrees commented Oct 19, 2024

Snyk has created this PR to upgrade autoprefixer from 10.4.19 to 10.4.20.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 3 months ago, on 2024-08-02.
Release notes
Package name: autoprefixer
  • 10.4.20 - 2024-08-02
    • Fixed fit-content prefix for Firefox.
  • 10.4.19 - 2024-03-20
    • Removed end value has mixed support, consider using flex-end warning since end/start now have good support.
from autoprefixer GitHub release notes
Commit messages
Package name: autoprefixer

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@fibble fibble changed the title [Snyk] Upgrade autoprefixer from 10.4.19 to 10.4.20 chore: pgrade autoprefixer from 10.4.19 to 10.4.20 [Snyk] Oct 28, 2024
@fibble fibble merged commit 1fdc262 into main Oct 28, 2024
20 checks passed
@fibble fibble deleted the snyk-upgrade-b6f07009b66e1bce14176c6f55c08259 branch October 28, 2024 12:50
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.

4 participants