ci: Drop gemfile.locks and stabilize the CI (preparation for graphql-2.3.) compatibility #281
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, we're working on making this gem support
graphql-ruby
2.3. (our fork already supports and the version is live on production.In order to prepare for the 2.3. compatibility changes we had to stabilize the CI a little:
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..ruby-version
used in development to 3.2.0. I think it should be fine as 2.7.5 is quite old alreadygraphl-2.0
appraisal to2.0.19
as newer patch versions were not backwards compatible which started crashing CI. I'll upgrade it in the next PR