-
Notifications
You must be signed in to change notification settings - Fork 41
Update CI matrix and Gemfile for multi-version grape testing #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
Update CI matrix and Gemfile for multi-version grape testing #76
Conversation
- Expand test matrix in .github/workflows/test.yml to include various ruby and grape version combinations (1.8.0, 2.0.0, 2.1.3, 2.2.0, HEAD). - Update Ruby setup to utilize new matrix entries. - Add conditional gem specification for grape in Gemfile based on GRAPE_VERSION environment variable.
To much. |
…ing of grape, grape-swagger, and grape-entity
- Test grape, grape-swagger, and grape-entity with one stable and one development version each. - Reduce total combinations to improve speed and maintainability without sacrificing essential coverage.
…e-entity versions
Much better now. |
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.
Thanks for doing this!
Personally I dislike having to use include
and exclude
to limit the exploding matrix. The one in Grape is particularly egregious (https://github.com/ruby-grape/grape/blob/master/.github/workflows/test.yml#L22). I much prefer explicit declarations like in https://github.com/slack-ruby/slack-ruby-client/blob/master/.github/workflows/test.yml#L8. Maybe someone feels as strongly as me about it ;)
This PR makes it easier for us to test the gem with different versions of grape and Ruby. By expanding our test matrix and updating the Gemfile, we can check that our changes work with a wider range of grape versions. This helps catch any issues early and ensures our gem stays compatible with future updates.