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

An in-range update of styled-components is breaking the build 🚨 #6

Open
greenkeeper bot opened this issue May 30, 2019 · 7 comments
Open

An in-range update of styled-components is breaking the build 🚨 #6

greenkeeper bot opened this issue May 30, 2019 · 7 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented May 30, 2019

The dependency styled-components was updated from 4.2.0 to 4.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

styled-components is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 30, 2019

After pinning to 4.2.0 your tests are passing again. Downgrade this dependency 📌.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jun 5, 2019

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for v4.3.0
  • Make it possible to initialize SC_ATTR and SC_DISABLE_SPEEDY via REACT_APP_* .env variables for easier integration with CRA applications (see #2501)

  • Fix components being folded inappropriately when an interim HOC is present (see #2586)

  • Fix theme prop for styled native components, also fixes theme in
    defaultProps for them (see #2576)

  • Add "forwardedAs" prop to allow deeply passing a different "as" prop value to underlying components
    when using styled() as a higher-order component (see #2580)

  • Implement defaultProps folding (see #2597)

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jun 6, 2019

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for v4.3.1
  • Revert #2586; breaks rehydration in dev for certain runtimes like next.js

We'll explore reintroducing it in v5 but better safe than sorry.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 23, 2019

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for v4.4.0

This is the last minor release before v5, please start using the beta and give us feedback!

This is a minor release not a patch release due to this change: #2738. Apologies if this causes some code churn in your projects, as it was a long-standing bug that needed fixing.

  • Fix to use ownerDocument instead of global document, by @yamachig (see #2721)

  • Backport fix for SSR classname mismatches in development mode for some environments like next.js (see #2701)

  • Fix attrs not properly taking precedence over props

  • Backport fix where classnames are composed in the wrong order if custom class names are passed in (see #2760)

  • Fix add check for style tag detached - sheet in the style tag is null in this case, by @newying61 (see #2707)

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Oct 30, 2019

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for v4.4.1
  • Fix styled-components's react-native import for React Native Web, by @fiberjw (see #2797)

  • Remove dev-time warning if referencing a theme prop without an outer ThemeProvider, the check for it isn't smart enough to handle cases with "or" or ternary fallbacks and creates undesirable noise in various third party integrations

@luckyfor
Copy link

luckyfor commented Dec 5, 2020

hi

@luckyfor
Copy link

luckyfor commented Dec 5, 2020

hihi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant