Ransack 3.0.0

[scarroll32]

The next release of Ransack will be a major version bump: 3.0.0 🚀

• With this release there will be a special announcement from @ernie, the creator of Ransack.

These issues and PRs are targeted for this release:

• Rename master to `main @scarroll32
• Remove deprecated #search method
• Merge Wiki and README into a GitHib Pages site @scarroll32
• Dropping support for 5.2 @deivid-rodriguez
• Update the Ransack Logo @scarroll32
• Allow scopes that define string SQL joins @mhssmnn - this just needs a note in the README

These can also be added if tests added / passing CI:

• Respect ransack_alias when sorting related tables @ekampp (released as 2.5.0, introduced by Enable sort using alias #1223)
• Added remove_association_no_negative_assoc to config to allow user to… @Doctor06
• Revert a change made in 2014 that prevent Ransack from finding the co @scarroll32
• Consider ransack aliases when sorting @faragorn (released as 2.5.0, introduced by Enable sort using alias #1223)
• Evaluate ransackable_scopes before attributes @faragorn
• Add the helper search_form_with @scarroll32
• sort_link class: does not get passed correctly when no label argument passed (SortLink.new) @deivid-rodriguez

[scarroll32]

CC @y-yagi

[MatthewKennedy]

Adding the ability to search on Rails 7 encrypted columns encrypts :email, deterministic: true, would be pure genius and well 3.0 worthy.

[scarroll32]

We're going to release this soon - stay turned!

[deivid-rodriguez]

Two of the PRs in the second list have already been introduced, I marked them as complete! 🎉

Also, the remaining items in the first list or "repository management tasks", so no really blockers for any release, no?

I plan to make this release the 24th of March.

[scarroll32]

I plan to make this release the 24th of March.

@deivid-rodriguez this sounds like a great target date. Can we have a check-in around the 20th?

[scarroll32]

@deivid-rodriguez is there anything else you think we should add to 3.0.0?

[deivid-rodriguez]

No, not really, my plan is to simply release what's pending to be released (if there's anything) every two weeks. Hence the target date of two weeks from today, since I just released 2.6.0.

[scarroll32]

No, not really, my plan is to simply release what's pending to be released (if there's anything) every two weeks. Hence the target date of two weeks from today, since I just released 2.6.0.

This is a great idea in general, and maybe we can even automate releases. 🤔

I'd like to make the 3.0.0 release special as it is the change to add any breaking changes as well as a major milestone, so maybe we will need a couple more days, but let's target the 24th.

[deivid-rodriguez]

Is there any pending breaking change that you want to make?

[scarroll32]

Is there any pending breaking change that you want to make?

I believe this is a breaking change. Not sure if there are any others.

[deivid-rodriguez]

Yes, that's the one we'll introduce for sure. Also the fix for #1277 apparently has the chance to break some usages so I will probably introduce that too.

[scarroll32]

Also the fix for #1277 apparently has the chance to break some usages so I will probably introduce that too.

Added it to the list of optionals.

[scarroll32]

@MatthewKennedy

Adding the ability to search on Rails 7 encrypted columns encrypts :email, deterministic: true, would be pure genius and well 3.0 worthy.

Here's the tracking issue

[scarroll32]

3.0.0 is published on RubyGems.

Thanks for your help @deivid-rodriguez and everyone who contributed to this release. ☘️