- Published on
I’ve spent the better part of the last decade doing two things that, at first glance, couldn’t seem more different: maintaining WPGraphQL and coaching youth soccer.
I’ve spent the better part of the last decade doing two things that, at first glance, couldn’t seem more different: maintaining WPGraphQL and coaching youth soccer.
As WPGraphQL continues to power more decoupled WordPress applications — from startups to enterprise-scale projects — access control is becoming a more common topic of concern. One area that often prompts discussion is whether exposing users via the GraphQL API poses a security risk.
Publishing a new release for WPGraphQL has historically required several manual steps—updating changelogs, determining semantic version bumps, preparing upgrade notices, and ensuring that every piece of documentation reflects the correct information. While I had a process in place, it wasn’t as efficient as it could be, and the potential for human error was always there.
🚀 WPGraphQL v2.0.0 has officially been released! This is a major update that includes breaking changes, so if you’re using WPGraphQL in production, please review the details below to ensure a smooth upgrade.
We’re excited to announce that WPGraphQL v2.0 is coming soon! This release brings key improvements such as better performance, stricter validation, and more flexibility for developers.
WPGraphQL v2.0 is coming soon, featuring an upgrade to its underlying GraphQL engine, graphql-php, from v14.11.10 to v15.8.1.
Last week at WASMCon 2024, I had the privilege of speaking about something I’m incredibly passionate about: using WordPress in non-traditional ways. My talk, “WordPress Meets WASM: Full Power of the CMS in Any App,” explored how WordPress, a platform many associate with traditional websites, can now be embedded and run virtually anywhere, thanks to technologies like WebAssembly (WASM).
We’re excited to announce that WPGraphQL v1.29.2 now supports Live Preview functionality on WordPress.org, powered by WordPress Playground. This integration makes it easier than ever for developers to experience WPGraphQL firsthand without any installation or setup required.
Before diving into the details of this announcement, I want to address something important. I am, like all of you, a human being. Given the current tensions in the WordPress ecosystem, my decision to move from WP Engine to Automattic might evoke strong feelings. Whether you agree or disagree with this decision, please recognize me as a human. Please treat me with respect, even if you strongly oppose my choices. The WordPress community is one I care deeply about, and we all benefit from respectful dialogue, no matter our differences.
Hello WPGraphQL Community,