Skip to content

Conversation

LeipeLeon
Copy link

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

Also made these decisions:

  • Setup appraisals for all major.minor versions of active[support|model] >= 6
  • Test w/ faraday 1.x & 2.x on various ruby's and latest active[support|model]
    • ruby: 3.0, 3.1, 3.2, 3.3, 3.4
  • When all ruby test passes run all combinations of ruby/faraday/active[support|model]
    • ruby: 3.0, 3.1, 3.2, 3.3, 3.4
    • faraday: 1.x, 2.x
    • activesupport/activemodel: 6.0, 6.1, 7.0, 7.1 ,7.2, 8.0
    • Exclude unsupported versions:
      • activesupport ~> 7.2.0 depends on Ruby >= 3.1.0
      • activesupport ~> 8.0.0 depends on Ruby >= 3.2.0
  • Added mutex_m and base64 to the development dependencies to make tests pass.
  • Updated the README with basic instructions for local development.

image

- setup matrix for all major.minor versions of activesupport/activemodel >= 6
- run these against both versions of faraday
- run tests w/ the generated gemfiles so when a ruby version fails it's shown as a separate failure in GHA
…ger (NameError)

`concurrent-ruby` v1.3.5 has removed the dependency on logger`

> require logger and leave concurrent-ruby version unlocked. This is primarily an issue for older Rails 7.0 and 6.1.

ruby-concurrency/concurrent-ruby@d7ce956

See: https://stackoverflow.com/questions/79360526/uninitialized-constant-activesupportloggerthreadsafelevellogger-nameerror
```
/home/runner/work/json_api_client/json_api_client/gemfiles/vendor/bundle/ruby/3.4.0/gems/activesupport-6.0.6.1/lib/active_support/notifications/fanout.rb:3: warning: mutex_m was loaded from the standard library, but is not part of the default gems starting from Ruby 3.4.0.
You can add mutex_m to your Gemfile or gemspec to silence this warning.

/home/runner/work/json_api_client/json_api_client/gemfiles/vendor/bundle/ruby/3.4.0/gems/webmock-3.5.1/lib/webmock/util/headers.rb:1: warning: base64 was loaded from the standard library, but is not part of the default gems starting from Ruby 3.4.0.
You can add base64 to your Gemfile or gemspec to silence this warning.
```
as done on my machine
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