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.27.2 to 1.28.1 #4175

Closed

Conversation

dependabot[bot]
Copy link
Contributor

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

Bumps wp-graphql/wp-graphql from 1.27.2 to 1.28.1.

Release notes

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

v1.28.1

Release Notes

Chores / Bugfixes

  • #3189: fix: [regression] missing placeholder in $wpdb->prepare() call

Full Changelog: wp-graphql/wp-graphql@v1.28.0...v1.28.1

v1.28.0

Upgrade Notice

This release contains an internal refactor for how the Type Registry is generated which should lead to significant performance improvements for most users.

While there are no intentional breaking changes, because this change impacts every user we highly recommend testing this release thoroughly on staging servers to ensure the changes don't negatively impact your projects.

New Features

  • #3172: feat: only eagerlyLoadType on introspection requests.

Chores / Bugfixes

  • #3181: ci: replace docker-compose commands with docker compose
  • #3182: ci: test against WP 6.6
  • #3183: fix: improve performance of SQL query in the user loader

Full Changelog: wp-graphql/wp-graphql@1.27.2...v1.28.0

Changelog

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

1.28.1

Chores / Bugfixes

  • #3189: fix: [regression] missing placeholder in $wpdb->prepare() call

1.28.0

Upgrade Notice

This release contains an internal refactor for how the Type Registry is generated which should lead to significant performance improvements for most users.

While there are no intentional breaking changes, because this change impacts every user we highly recommend testing this release thoroughly on staging servers to ensure the changes don't negatively impact your projects.

New Features

  • #3172: feat: only eagerlyLoadType on introspection requests.

Chores / Bugfixes

  • #3181: ci: replace docker-compose commands with docker compose
  • #3182: ci: test against WP 6.6
  • #3183: fix: improve performance of SQL query in the user loader
Commits
  • 6516f75 Merge pull request #3193 from wp-graphql/release/v1.28.1
  • 46996cb Merge commit '43fa32c8b3f470dc0541739eaa0f7d3d6ab30a2d' into release/v1.28.1
  • 909b4c8 - update versions, changelog for release
  • 43fa32c Merge pull request #3189 from justlevine/fix/missing-placeholder-wpdb
  • c21332f fix: try with unquoted complex placeholders
  • 9478e7e chore: fix spacing
  • e468d65 chore: annotation typo
  • f593aba fix: dont interpolate $ids in wpdb::prepare
  • 66aaf9a Auto-merge master back to develop
  • e6983cd Merge pull request #3185 from wp-graphql/develop
  • 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]
wp-graphql/wp-graphql [>= 1.16.a, < 1.17]
wp-graphql/wp-graphql [>= 1.20.a, < 1.21]
wp-graphql/wp-graphql [>= 1.21.a, < 1.22]

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.27.2 to 1.28.1.
- [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@1.27.2...v1.28.1)

---
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>
@alexkuc
Copy link

alexkuc commented Sep 2, 2024

@tn3rb I'll prepare a PR for Cafe as it is good to bring this into upstream

v1.28.0
...
This release contains an internal refactor for how the Type Registry is generated which should lead to significant performance improvements for most users.

Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 1, 2024

Superseded by #4179.

@dependabot dependabot bot closed this Oct 1, 2024
@dependabot dependabot bot deleted the dependabot/composer/wp-graphql/wp-graphql-1.28.1 branch October 1, 2024 22:57
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.

2 participants