Commit Graph

7 Commits

Author SHA1 Message Date
Peter Goldstein 3e57eb531f
Add Ruby 3.1 to CI (#558)
* Add Ruby 3.1 to CI

Update Rubocop for recent Rubies
Disable Rubocop run for Rubies before Ruby 2.4
Quote '3.0' in the CI configuration to ensure it loads a 3.0.x Ruby
Set RUBYOPT="--disable_error_highlight" so Ruby 3.1 error matchers pass

* Add CHANGELOG.md entry

* Re-add deleted line from CHANGELOG.md

* Set minimum supported Ruby version to 2.4.

Remove a number of code bits designed to support Rubies below version 2.4

* Bump version.  Remove unneeded require from Gemfile.  Add require to spec/support file
2022-01-27 18:59:24 -08:00
Michael Herold f50cf8e6bb Bring integration tests into main test harness
We have a nice integration spec harness, so let's make sure we use it
when we're working on the gem. I'm making the following changes:

* Make `bundle exec rake` run integration specs, except on Travis.
* Silence a warning in the OmniAuth integration spec that has nothing to
  do with Hashie.
* Make Guard run integration specs when appropriate. Now, when you run
  all tasks you will run integration specs. Also, if you modify an
  integration spec, it will run. Lastly, if you modify anything in `lib`
  the integration specs will run.
* Keeps the extra Travis build that only runs integration specs. Travis
  didn't like the Rake task that included it and there's extra signal by
  doing it this way anyway.
2017-02-03 15:20:21 -06:00
dblock acc3d48b91 Upgraded to RuboCop 0.34.2. 2015-10-25 15:22:45 -04:00
dB 8244d4456b Fix: working guard. 2014-08-24 13:22:25 -04:00
Michael Herold 270e948d08 Update Rubocop to 0.25.0 and get it passing 2014-08-23 10:18:22 -05:00
Michael Bleigh 5513b967b2 Remove reference to singleton_class, that's Ruby 1.9 only. 2011-08-02 17:23:13 -05:00
Michael Bleigh d01a163b69 Switch to Bundler for gem management and Guard for autotesting. 2011-07-22 16:33:18 -05:00