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

Bump wp-graphql/wp-graphql from 1.12.0 to 1.16.0 #4159

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 1, 2023

Bumps wp-graphql/wp-graphql from 1.12.0 to 1.16.0.

Release notes

Sourced from wp-graphql/wp-graphql's releases.

v1.16.0

Release v1.16.0

Upgrade Notice

WPGraphQL Smart Cache

For WPGraphQL Smart Cache users, you should update WPGraphQL Smart Cache to v1.2.0 when updating WPGraphQL to v1.16.0 to ensure caches continue to purge as expected.

Cursor Pagination Updates

This version fixes some behaviors of Cursor Pagination which may lead to behavior changes in your application.

As with any release, we recommend you test in staging environments. For this release, specifically any queries you have using pagination arguments (first, last, after, before).

New Features

  • #2918: feat: Use graphql endpoint without scheme in url header.
  • #2882: feat: Config and Cursor Classes refactor

Full Changelog: wp-graphql/wp-graphql@v1.15.10...v1.16.0

v1.15.0

Release Notes

New Features

Chores / Bugfixes

v1.14.10

Release Notes

Chores / Bugfixes

... (truncated)

Changelog

Sourced from wp-graphql/wp-graphql's changelog.

1.16.0

Upgrade Notice

WPGraphQL Smart Cache For WPGraphQL Smart Cache users, you should update WPGraphQL Smart Cache to v1.2.0 when updating WPGraphQL to v1.16.0 to ensure caches continue to purge as expected.

Cursor Pagination Updates This version fixes some behaviors of Cursor Pagination which may lead to behavior changes in your application.

As with any release, we recommend you test in staging environments. For this release, specifically any queries you have using pagination arguments (first, last, after, before).

New Features

  • #2918: feat: Use graphql endpoint without scheme in url header.
  • #2882: feat: Config and Cursor Classes refactor

1.15.0

New Features

Chores / Bugfixes

1.14.10

Chores / Bugfixes

  • #2874: fix: improve PostObjectCursor support for meta queries. Thanks @​kidunot89!
  • #2880: fix: increase clarity of the description of "asPreview" argument

1.14.9

Chores / Bugfixes

... (truncated)

Commits
  • 9342909 Merge pull request #2922 from wp-graphql/release/v1.16.0
  • b5ee4c9 Merge commit '20f38c5b914f24134e4244a6104eecf27b562a00' into release/v1.16.0
  • 53e1aea - update versions, changelog for release
  • 20f38c5 Merge pull request #2882 from kidunot89/feat/post-object-cursor-filters
  • 30d3622 Merge pull request #2918 from wp-graphql/revert-2911-revert-2904-fix/cache-ke...
  • da3476f Merge branch 'develop' into feat/post-object-cursor-filters
  • 7d5b56c - rename threshold fields
  • 2d9e6c0 Revert "revert: "fix: Use graphql endpoint without scheme in url header""
  • 1934b33 Merge commit 'd85b112abb853e13167ef21726afcc6b1c4fa949' into feat/post-object...
  • f7b5e08 - rename is_valid_threshold_field to validate_threshold_field
  • Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name Ignore Conditions
wp-graphql/wp-graphql [>= 1.14.a, < 1.15]
wp-graphql/wp-graphql [>= 1.13.a, < 1.14]

Dependabot compatibility score

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)

Bumps [wp-graphql/wp-graphql](https://github.com/wp-graphql/wp-graphql) from 1.12.0 to 1.16.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.16.0)

---
updated-dependencies:
- dependency-name: wp-graphql/wp-graphql
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@tn3rb
Copy link
Member

tn3rb commented Jan 8, 2024

@dependabot ignore this minor version

@dependabot dependabot bot closed this Jan 8, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 8, 2024

OK, I won't notify you about version 1.16.x again, unless you re-open this PR.

@dependabot dependabot bot deleted the dependabot/composer/wp-graphql/wp-graphql-1.16.0 branch January 8, 2024 18:02
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.

1 participant