Skip to content
This repository was archived by the owner on May 6, 2024. It is now read-only.

Improve the Github Action for testing various combinations of ruby/faraday/active[support|model] #3

Open
wants to merge 10 commits into
base: seb-faraday-2.x
Choose a base branch
from

Conversation

LeipeLeon
Copy link

I took the liberty to update the Github action to improve the tests

Also made these decisions:

  • drop support for rails < 6.0. It's no longer maintained.
    See: https://www.fastruby.io/blog/ruby/rails/versions/compatibility-table.html

  • setup appraisals for all major/minor versions of active[support|model] >= 6

  • test w/ faraday 1.x & 2.x on various ruby's

    • faraday-gzip depends on Ruby (>= 2.6, < 4) so <= 2.5 is out the window
    • run tests w/ the generated gemfiles
  • when ruby test passes run all combinations of ruby/faraday/active[support|model]

    • ruby: 2.6, 2.7, 3.0, 3.1, 3.2
    • faraday: 1.x, 2.x
    • activesupport/active_model: 6.0, 6.1, 7.0, 7.1
    • exclude ruby 2.6 / activesupport >= 7.0
      b/c required ruby >= 2.7.0

Note: The github action is partial copied from https://github.com/LeipeLeon/rails_key_rotator/blob/main/.github/workflows/main.yml

tapajos and others added 10 commits November 25, 2023 11:18
- drop support for rails < 6.0
  See: https://www.fastruby.io/blog/ruby/rails/versions/compatibility-table.html
- setup matrix for all major/minor versions of activesupport/activemodel >= 6
-
- [`faraday-gzip`](https://rubygems.org/gems/faraday-gzip/versions/2.0.0) depends on Ruby (>= 2.6, < 4) so <= 2.5 is out the window
- run tests w/ the generated gemfiles (parial copied from <https://github.com/LeipeLeon/rails_key_rotator/blob/main/.github/workflows/main.yml>)
…port|model]

- ruby: 2.6, 2.7, 3.0, 3.1, 3.2
- faraday: 1.x, 2.x
- activesupport/active_model: 6.0, 6.1, 7.0, 7.1
- exclude ruby 2.6 / [activesupport >= 7.0](https://rubygems.org/gems/activesupport/versions/7.0.8)
  b/c required ruby >= 2.7.0
@LeipeLeon
Copy link
Author

ping @lavoiesl

Do you have any feedback on this PR? or should I wait when your branch is merged w/ upstream.

@lavoiesl
Copy link

The general idea LGTM, but I haven't reviewed in details

Since this PR doesn't add any functionality that would be a blocker for Shopify development, I would suggest only opening a PR upstream.

@lavoiesl lavoiesl force-pushed the seb-faraday-2.x branch 5 times, most recently from 26f873f to 1db00ea Compare May 2, 2024 20:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants