-
Notifications
You must be signed in to change notification settings - Fork 87
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
Bump wp-graphql/wp-graphql from 1.12.0 to 1.24.0 #4166
Bump wp-graphql/wp-graphql from 1.12.0 to 1.24.0 #4166
Conversation
Bumps [wp-graphql/wp-graphql](https://github.com/wp-graphql/wp-graphql) from 1.12.0 to 1.24.0. - [Release notes](https://github.com/wp-graphql/wp-graphql/releases) - [Changelog](https://github.com/wp-graphql/wp-graphql/blob/develop/CHANGELOG.md) - [Commits](wp-graphql/wp-graphql@v1.12.0...v1.24.0) --- updated-dependencies: - dependency-name: wp-graphql/wp-graphql dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
@tn3rb If possible… let's action this. The current version of wpgraph is created in Oct 10, 2022. There is one possible breaking change which I can investigate. If we proceed, it would nicely tie in with Barista's issue for reviewing GraphQL types. Additionally, there is minor updating required for the PHP. I can do _both. Why both? Since the backend (PHP) feeds the frontend (TS/React), it would allow me to become more familiar with how GraphQL is configured since, after all, we do use custom types on it. I won't proceed with anything for now, I'll wait for your decision. |
we'll need to update the WP GQL version in the Cafe monorepo. This is the legacy core repo and is only used now for public access to core. All development and updates happen in Cafe now, so we can create a branch there for updating WP GQL. |
Yeah, I can do that. Is it okay for me to proceed with PR for updating GraphQL in cafe monorepo? |
absolutely dude |
Will be implemented in https://github.com/eventespresso/cafe/issues/1281 hence closing this issue |
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps wp-graphql/wp-graphql from 1.12.0 to 1.24.0.
Release notes
Sourced from wp-graphql/wp-graphql's releases.
... (truncated)
Changelog
Sourced from wp-graphql/wp-graphql's changelog.
... (truncated)
Commits
88af688
Merge pull request #3102 from wp-graphql/release/v1.24.0545cc52
Merge commit 'a6173b658dea998bf4735c4f418eada25a481615' into release/v1.24.0b3d6d23
- update versions, changelog, upgrade notice for releasea6173b6
Merge pull request #3095 from justlevine/chore/superfluous-whitespace4032c4c
- composer fix-cs36b9475
Merge commit '2d5c97efcbb1e679bd83c5b743810fbf0f87432d' into chore/superfluou...2d5c97e
Merge pull request #3101 from wp-graphql/chore/connection-resolvers-cleanupf7309af
Merge pull request #3083 from wp-graphql/dev/cr2-backport/deprecate-camelcased89491b6
Merge commit '0504a22b5ff0f6fb7dc960cf669b03873543f572' into dev/cr2-backport...0504a22
Merge pull request #3085 from wp-graphql/dev/prepare_page_infoMost Recent Ignore Conditions Applied to This Pull Request
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)