From 6660c8eebbbacfd3200172085254e22ca6475174 Mon Sep 17 00:00:00 2001 From: Zee Spencer Date: Tue, 1 Mar 2022 14:25:59 -0800 Subject: [PATCH] Bypass using the `pre`release versions of rspec Here, @pirj shows us how to use the Rails 7 compatible branch: - https://github.com/rspec/rspec-rails/pull/2546#issuecomment-1009302646 Then, I got confused about what to do with the other changes: - https://github.com/rspec/rspec-rails/pull/2546#issuecomment-1017228243 So, to make it a bit easier to just "drop in" a the ActionMailer fixes, this branch makes rspec-rails "feel like" a released version of itself, so bundling off of it doesn't incidentally pull in the pre-release version of rspec. There's nothing wrong with the pre-release version of rspec, but I'm not particularly confident making the recommended other changes to my consuming applications codebase; so a quick fork until a real 5.1.1 or 6.0 release comes out seems "safest" --- lib/rspec/rails/version.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/rspec/rails/version.rb b/lib/rspec/rails/version.rb index ef294c460..20f63c6d8 100644 --- a/lib/rspec/rails/version.rb +++ b/lib/rspec/rails/version.rb @@ -3,7 +3,7 @@ module Rails # Version information for RSpec Rails. module Version # Current version of RSpec Rails, in semantic versioning format. - STRING = '5.1.0.pre' + STRING = '5.1.1' end end end