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

Feat: launch gatsby-source-wordpress v4 (#29150) #29330

Merged
merged 3 commits into from
Feb 4, 2021

Conversation

vladar
Copy link
Contributor

@vladar vladar commented Feb 4, 2021

Backporting #29150 to the 2.32 release branch.

Fixed a single conflict in package/gatsby-source-wordpress/package.json

(cherry picked from commit 862637b)

Co-authored-by: Vladimir Razuvaev <vladimir.razuvaev@gmail.com>
Co-authored-by: Ward Peeters <ward@coding-tech.com>
Co-authored-by: gatsbybot <mathews.kyle+gatsbybot@gmail.com>

(cherry picked from commit 862637b)
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Feb 4, 2021
@vladar vladar added type: cherry and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Feb 4, 2021
"author": "Sebastien Fichot <fichot.sebastien@gmail.com>",
"description": "Source data from WordPress in an efficient and scalable way.",
"author": "Tyler Barnes <tylerdbarnes@gmail.com>",
"version": "4.0.0-next.0",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The only change from the original PR here: replaced 4.1.0-next.0 with 4.0.0-next.0 as we'll publish 4.0.0 from this release branch.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Also had to update dependency versions (missed that at first): 988413c

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Also looks like yarn.lock wasn't updated in the original PR.

wardpeet
wardpeet previously approved these changes Feb 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants