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

fix(deps): update dependency postcss-normalize to v13 #1131

Merged
merged 1 commit into from
Sep 16, 2024

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 7, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
postcss-normalize ^10.0.1 -> ^13.0.0 age adoption passing confidence

Release Notes

csstools/postcss-normalize (postcss-normalize)

v13.0.0

Compare Source

  • Pin versions of @csstools/normalize.css and sanitize.css

v12.0.0

Compare Source

  • Remove TypeScript types. This package is a dual published cjs and esm and it isn't worth it, all info is in README.md.
  • Set minimum node version to 18
  • Fix resolution of @csstools/normalize.css path when using ESM

v11.0.0

Compare Source

  • Cleanup build dependencies

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Sep 7, 2024
@GoetzGoerisch GoetzGoerisch merged commit 93ec6ae into umati Sep 16, 2024
14 checks passed
@renovate renovate bot deleted the renovate/postcss-normalize-13.x branch September 16, 2024 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant