Open
Conversation
Fix Rails 6 and Rails 6.1 Builds
Support for Rails 6.1
…aky_test Fix flaky test which would fail in certain timezones
Improved custom audit user section in README
Fixed small typo in README
Fix coverage issue
Rails 6.1 introduced a change of ActiveRecord configurations. Now we get a deprecation warning saying should use `configs_for. Here we check AR version and if it's newer than 6.1, use the latest API and `Tasks` for simpler setup.
…state Use Thread local variables instead of Fibers
…st-rails-61 Fix CI against Rails 6.1
…uby-27-deprecations Fix Rails 6.1 deprecations
…s-42 Drop Rails 4.2 support
…ssociated_audits_for_sti own_and_associated_audits for STI
…or-on-load Follow Rails autoloading conventions
Updated readme for initializer file name.
…ed-enum-flag Restore previous enum behavior with flag
Remove our rubocop config
That matches our old Rubocop config
…ils-7.2 Clean up Appraisal and CI config; add Rails 7.2 and Ruby 3.3
Rails 8 does not have an alpha or beta rubygems release, but it sounds like a release is imminent (to coincide with Rails World in late September). To prepare for Rails 8, this PR relaxes the Rails requirement in the audited gemspec to allow "< 8.1" instead of "< 8.0". This will allow audited to be used with Rails 8.0 when it is released. To test that audited will work with Rails 8, I added a `rails-main` Gemfile to `Appraisals` that targets the Rails main branch, and included this in the CI matrix.
Relax gemspec to allow Rails 8.0; add Rails main branch to CI
Relax gemspec to allow Rails 8.1
…lling_audited_multiple_times allow calling audited multiple times
Add Rails 8.0 to build matrix
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why is this needed? (Not sure of the original intention but based on reading the code and my understanding)
namespaced_conditionswas introduced to track theservice_name