Find packages/gatsby/package.json in files changed and keep this tab open for reference.Click on the version, then click on commit called chore(release): Publish.Pick a version that you'd like to rollback to from here.In the end I rolled back my gatsby version to what it was before: ~2.13.x Steps to reproduce Currently, I have all sorts of incompatibility issues that break my builds, which is due to all gatsby's own dependencies being newer than gatsby itself. What I would like to do is be able to add a version of gatsby at the time it was released. I tried to pin versions of gatsby-cli by adding the following to "^2.7.0" See - + - broken - Error: Reducers may not dispatch - broken - activities of undefined error (yoga + - broken - Error: Reducers may not dispatch - broken - Error: Reducers may not dispatch + - broken - Error: Reducers may not dispatch - broken ![]() ![]() These are headline summaries of me trying to pin versions of gatsby with versions of gatsby-cli (it was pointed out in one of the issues that a version of gatsby-cli should be + - broken - Error: Reducers may not dispatch - broken - activities of undefined error (yoga layout) I found that the problem was in a particular version of gatsby, so I thought if I simply roll it back to a version before the issue was introduced, it would work smoothly. Describe the issue that you're seeing.I decided to upgrade a bunch of outdated gatsby dependencies (see a screenshot from the PR below).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |