Skip to content

Conversation

@pieh
Copy link
Contributor

@pieh pieh commented Mar 5, 2019

fixes #12307

Copy link
Contributor

@DSchau DSchau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe just make this a little helper since we're basically copy/pasting here?

Didn't realize it was separate plugins 🤦‍♂️ Looks good!

@DSchau DSchau changed the title fix: don't crash if cpu-core-count is not available fix(*): don't crash if cpu-core-count is not available Mar 5, 2019
@DSchau
Copy link
Contributor

DSchau commented Mar 5, 2019

@pieh for the lint failure, see #12334

@pieh
Copy link
Contributor Author

pieh commented Mar 5, 2019

@pieh for the lint failure, see #12334

Nice, merged that one and updated this branch so it can be nice and green ;)

Copy link
Contributor

@DSchau DSchau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@DSchau
Copy link
Contributor

DSchau commented Mar 5, 2019

Wish there was a conventional changelog message for multiple, e.g.

fix(gatsby-plugin-sharp, gatsby-plugin-manifest): fix some issue

@DSchau DSchau merged commit 412217d into gatsbyjs:master Mar 5, 2019
@pieh pieh deleted the cpu-count-fallback branch March 5, 2019 21:31
@DSchau
Copy link
Contributor

DSchau commented Mar 5, 2019

Successfully published:

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.

gatsby-plugin-sharp 2.0.24 requires [email protected] but specifies peer dependency of gatsby@^2.0.0

3 participants