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

ci: Drop gemfile.locks and stabilize the CI (preparation for graphql-2.3.) compatibility #281

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

Bajena
Copy link

@Bajena Bajena commented Sep 10, 2024

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:

  • It's not the best 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.
  • I also updated the rack development dependency in the gemspec and locked it to version 2.0 because of the breaking changes in version 3 that were crashing the CI.
  • I upgraded the .ruby-version used in development to 3.2.0. I think it should be fine as 2.7.5 is quite old already
  • I locked graphl-2.0 appraisal to 2.0.19 as newer patch versions were not backwards compatible which started crashing CI. I'll upgrade it in the next PR
  • I fixed rubocop offenses (mainly repeated context names, no tests were changed)

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.
@Bajena Bajena changed the title Drop gemfile.locks and stabilize the CI (preparation for graphql-2.3.) compatibility fix: Drop gemfile.locks and stabilize the CI (preparation for graphql-2.3.) compatibility Sep 10, 2024
@Bajena Bajena changed the title fix: Drop gemfile.locks and stabilize the CI (preparation for graphql-2.3.) compatibility ci: Drop gemfile.locks and stabilize the CI (preparation for graphql-2.3.) compatibility Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant