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

[gatsby] Fix production build hanging on createPagesStatefully #3816

Closed
wants to merge 1 commit into from

Conversation

nsimonson
Copy link
Contributor

Fixes #3813

@nsimonson
Copy link
Contributor Author

I'd say it'd be good to make sure the AppVeyor build finishes this time, but because of this bug they're queued up for days.

@KyleAMathews
Copy link
Contributor

Deploy preview for using-glamor failed.

Built with commit be4fb97

https://app.netlify.com/sites/using-glamor/deploys/5a73dceedf99535000d2f472

@nsimonson
Copy link
Contributor Author

🤔Seems like the netlify builds are still hanging

@gatsbybot
Copy link
Collaborator

Deploy preview for gatsbygram ready!

Built with commit be4fb97

https://deploy-preview-3816--gatsbygram.netlify.com

aga5tya pushed a commit to aga5tya/aga5tya.me that referenced this pull request Feb 2, 2018
@Graham42
Copy link
Contributor

Graham42 commented Feb 2, 2018

If the globally installed version of gatsby is being used rather than the local one in node_modules will the Netlify builds ever work until we fix this bug?
I'm assuming (perhaps incorrectly) that Netlify auto-updates their environments to the latest version of gatsby. If so, this might mean the Netlify deploy with not work until this gets fixed. (ie. new version gets released)

@nsimonson
Copy link
Contributor Author

@KyleAMathews Once this is released we should deprecate gatsby@1.9.176 and gatsby@1.9.177 for folks who may have already upgraded.

@nsimonson
Copy link
Contributor Author

Closing in favor of 7bb93fe

@nsimonson nsimonson closed this Feb 2, 2018
@nsimonson nsimonson deleted the patch-1 branch February 2, 2018 19:35
@KyleAMathews
Copy link
Contributor

Oops sorry! I should have merged this instead :-( I didn't look through PRs this morning before fixing the problem (I'd noticed it when working on something)

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