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 polished to v4 #174

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 6, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
polished (source) 3.7.2 -> 4.2.2 age adoption passing confidence

Release Notes

styled-components/polished

v4.2.2

Compare Source

Bug Fixes

  • Color Modules - addresses an issue with longer floats in color values. (#​610 - Thanks to @​levymetal)

v4.2.1

Compare Source

Bug Fixes

  • hls(a) - now properly parses percentages for opacity.
  • rgb(a) - now properly parses percentages for opacity.

v4.2.0

Compare Source

Improvements

  • color Modules - now support space-separated CSS color values for rgb(a) and hsl(a). (#​605)
  • rgb - now accepts optional opacity value.
  • hsl - now accepts optional opacity value.

v4.1.4

Compare Source

Bug Fixes

  • mix - remove unnecessary division by 1 (#​59)

v4.1.3

Compare Source

Bug Fixes

  • Addressed several performance issues with regexes.

v4.1.2

Compare Source

Bug Fixes

  • fluidRange - updated return value to use an array to address unclear object property typing error in flow.

v4.1.1

Compare Source

Bug Fixes

  • scarf - removed scarf analytics package due to yarn incompatibilities and concerns over GDPR compliance.

v4.1.0

Compare Source

Introducing polished.js v4.1.0!

We're super stoked to announce that polished.js v4.1.0 is officially out! It is available via your package manager of choice. This will be the final non-patch release before v5.

npm install polished
yarn add polished

Release Highlights

New Module
  • remToPx: We've introduced a new module to handle converting to rem values to px values. (#​376)
Analytics
  • We are now leveraging Scarf to track package analytics. You can opt-out of this functionality by following these instructions

v4.0.5

Compare Source

Documentation

  • readableColor - Update docs and function signature to be clearer about the use of each parameter.

v4.0.4

Compare Source

Bug Fixes

  • transparentize - addressed an issue where we weren't handling cases where floats were greater than 2 decimals. (#​548)
  • npm - addressed an issue where .yarn cache was bloating published package size, along with some other ignore optimization. (#​553 Thanks @​scttcper)

v4.0.3

Compare Source

Bug Fix

v4.0.2

Bug Fix

  • ellipsis: Fixes an issue where the webkit prefix was not properly applied with the multiline option. (Thanks @​drakang4 - #​546)

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/polished-4.x branch 2 times, most recently from 7b20beb to 3f10743 Compare April 4, 2022 06:10
@renovate renovate bot changed the title fix(deps): update dependency polished to v4 Update dependency polished to v4 Dec 17, 2022
@renovate renovate bot changed the title Update dependency polished to v4 fix(deps): update dependency polished to v4 Dec 17, 2022
@renovate
Copy link
Contributor Author

renovate bot commented Mar 23, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

1 participant