-
Notifications
You must be signed in to change notification settings - Fork 82
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
fix: graphql-ruby 2.3 compatibility #282
base: main
Are you sure you want to change the base?
Conversation
It's a bad practice to commit Gemfile.lock files into gem repositories - `gemspec` files should be the source of truth for dependencies. I removed all Gemfile.lock files and updated the CircleCI configuration to use the Gemfile for cache keys. Additionally, I updated the `rack` development dependency in the gemspec and locked it to version 2.0 because of the breaking changes in version 3.
When can we expect this to be merged? |
@sethc2 could you please merge this? 🙏 or delegate to another maintainer? Thanks in advance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks good but because we utilize dependabot I think we generally prefer if we keep the Gemfile.lock. We follow Bundler's guidance here
Would you be opposed to adding the gemfile.lock(s) back in? We have been doing very little maintenance on this repository for the past couple years (see discussion here), and want to avoid any accidental breaking changes in dependencies.
requires merging #276 first
fixes #276
This PR:
graphql-ruby 2.3
Tracer
method to support the new way of module-based tracing (https://graphql-ruby.org/queries/tracing)trace_with
method in federated serviceswarden
method.