-
Notifications
You must be signed in to change notification settings - Fork 76
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
graphql 2.3.8 removes "warden", breaking schema composition etc #276
Comments
jeantessier
added a commit
to jeantessier/book-reviews
that referenced
this issue
Aug 15, 2024
for service in books reviews users search signatures jwts do echo '==========' $service '==========' (cd $service; bundle update --all) done echo '========== gateway ==========' (cd gateway; npm update) !!! BROKEN !!! BROKEN !!! BROKEN !!! BROKEN !!! BROKEN !!! It updated the `graphql` gem, but it still uses the same version of the `apollo-federation` gem. I might have to wait for that one to get an upgrade before things start working again. See Gusto/apollo-federation-ruby#276 and Gusto/apollo-federation-ruby#278
jeantessier
added a commit
to jeantessier/book-reviews
that referenced
this issue
Sep 15, 2024
./update.sh Still broken. Waiting on Gusto/apollo-federation-ruby#276
jeantessier
added a commit
to jeantessier/book-reviews
that referenced
this issue
Nov 10, 2024
for service in books reviews users search signatures jwts do echo '==========' $service '==========' ( cd $service # Edit Gemfile to push Rails dependency to "~> 8" bundle update --bundler bundle update --all bin/rails app:update # Fix PORT in development.rb # Fix PORT in puma.rb ) done Still broken. Waiting on Gusto/apollo-federation-ruby#276
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A change released in the 2.3.8 version of
graphql
removed thewarden
definition from a number of places, including this one:rmosolgo/graphql-ruby@v2.3.7...v2.3.8#diff-e9dd0d295a58b66fabd1cf717040de5a78ade0feac6aeabae5247b5785c029ab
It looks like the internal usage of
warden
was replaced withtypes
in many cases. This is documented in the release notes, but not as a breaking change.This is manifesting for us in CI builds as an error like the following:
The text was updated successfully, but these errors were encountered: