* Enforce no support for JR v0.10.0 yet in gemspec

* Ignore .bundle folder generated by Appraisal

* Update Appraisals semver constraints for jsonapi-resources

* Run CI against Rails 6

* Use ruby 2.5

* Dummy app updates for rails 6

* Run all but Rails 4.2 tests with Ruby 2.5

* Add empty asset manifest to appease Rails

Co-authored-by: Vesa Laakso <482561+valscion@users.noreply.github.com>

* Add better debuggability to be_X test failures

This way test failures will show what the HTTP status code actually was
when test fails as well as output the entire response body. The response
body will most likely contain vital debugging information to help figure
out why the test failed

* Output last request information on spec failures

* Add action. Update bundle and rake

* Skip bumping bundler and rake dependency

* Add gem file matrix to load rails version

* Add back ruby versions to matrix

* Change first ruby to 2.4

* Specify bundler version

* Starting with newer rails and ruby

* Update ruby.yml

* Revert bundle change

* Add another rails version

* Take ruby 3 out of the mix for this try

* Attempt to continue on error

* Run on all branches, full test matrix

* Fix Rails 4.2 / Ruby 2.3 runs

* Add Ruby 3.0

* Allow bundler 2.x

* Add bundler-version 2.1.4 to matrix

* Remove bundler-version 2.1.4 from matrix

* Add branch filter back to push

Co-authored-by: Vesa Laakso <vesa.laakso@venuu.fi>
Co-authored-by: Luke Street <luke.street@encounterpc.com>

* Drop support for Rails 4.2 and 5.1

Also use same versions of Rails 6.0, 5.2 and 5.1 as jsonapi-resources
v0.10.7 uses:
https://github.com/cerebris/jsonapi-resources/blob/v0.10.7/.github/workflows/ruby.yml

* Drop support for Ruby 2.6

* Avoid defining version of bundler used for GitHub actions

I discovered that this simple scenario wasn't tested properly when
working on JR 0.10 support

#146)

This can be a surprising behavior in jsonapi-authorization version that
supports JR 0.9. It will likely change when JR 0.10 is supported at some
point, if that time comes.

* Remove unused Rails 5.1 Appraisals

Seems like I forgot to remove these when I stopped testing with these
versions in CI

* Update rspec and rspec-rails to latest versions

* Update rake to 13.0

* Update phare to 1.0.1

* Verify code style in GitHub actions

* Update rubocop to version 1.35.1

* Fix renamed and moved rubocop style definitions

* Ignore auto-generated gemfiles for rubocop

* Fix changed rubocop department names

* Update targeted Ruby version to 2.7

* Configure rubocop to automatically enable new cops as they come

* Generate rubocop todo

* Fix Gemspec/OrderedDependencies

* Define that gem must be published with MFA

* Explicitly disable Gemspec/RequiredRubyVersion cop

* Fix Layout/EmptyLineAfterMagicComment

* Fix Layout/EmptyLineAfterGuardClause

* Remove most rubocop custom configurations

* Disable all Metrics department cops

* Disable Style/StringLiterals

* Autofix Style/SymbolArray

* Autofix Style/StructInheritance

* Autofix Style/StringConcatenation

* Autofix Layout/SpaceInsideHashLiteralBraces

* Autofix Style/AccessorGrouping

* Autofix Style/BlockDelimiters

* Autofix Style/ExpandPathArguments

* Autofix Style/RedundantFreeze

* Autofix Style/IfUnlessModifier

* Autofix Style/SignalException

* Autofix Style/Encoding

* Manually fix Lint/EmptyBlock

* Manually fix Naming/HeredocDelimiterNaming

* Autofix Style/CollectionCompact

* Autofix Lint/NonDeterministicRequireOrder

* Stop suggesting rubocop-rake and rubocop-rspec gems

* Disable Style/Documentation

* Autofix Style/FrozenStringLiteralComment

* Manually fix Style/GuardClause

* Manually fix Naming/MethodParameterName