Drop legacy dependencies support

[tagliala]

Hello, please review this approach to build the text matrix

Drop support for:

• Ruby < 3.1
• Rails < 7.0
• RGeo < 3 (close Let drop support for rgeo prior 3.0 #75)

---

Succesfull run: https://github.com/tagliala/rgeo-activerecord/actions/runs/10560520776

---

• Test against latest stable Ruby versions
• Test against AR 7.1 and 7.2
• Test against jruby-9.4.8.0 and jruby-head
• Mark edge/head tests as experimental to allow failures
• Update checkout actions
• Add explicit permissions for improved security

Ref: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions

[keithdoggett]

Thanks @tagliala this seems good to me. Only note may be to add AR 7.2 to the matrix as well.

[tagliala]

Done

[BuonOmo]

I'd also remove unmaintained ruby and activerecord versions (which ultimately might let us keep the original matrix?). WDYT?

[tagliala]

I'd also remove unmaintained ruby and activerecord versions (which ultimately might let us keep the original matrix?). WDYT?

You mean just remove from the matrix or drop support?

[BuonOmo]

drop support. But what do you have in mind more than removing it from the matrix ?

[tagliala]

But what do you have in mind more than removing it from the matrix ?

Change this:

rgeo-activerecord/rgeo-activerecord.gemspec

Line 15 in 06a42e3

spec.required_ruby_version = ">= 2.5.0"

Then I usually search documentation and source code because there may be references, conditional checks, or feature detection related to unsupported rails / ruby

Ref (just the latest thing I've worked on): jamesmartin/inline_svg#164

[tagliala]

Since 6.1 is going in EOL at the end of the month, I would go for

• Ruby >= 3.1
• Rails >= 7.0
• RGeo >= 3 (are 1.x/2.x considered legacy?)

[keithdoggett]

@tagliala looks good! Thank you. My only question is for @BuonOmo about the version and how to sequence releases.

[keithdoggett]

@BuonOmo will we have to synchronize this with the postgis adapter PR that you have up? Do we need a major version bump here?

[BuonOmo]

well since there is no change in the codebase, I don't think we have to do anything. TBH I would even consider not bumping major.

[tagliala]

major version bumped because of this approach. I can bump minor and change 8.0+ to 7.1+

[BuonOmo]

Version is not that important to me, I'll let you guys decide !

BTW @tagliala, is there any reason why the PR is still a draft?

[tagliala]

Status changed back to Open. This PR will close #75

[keithdoggett]

The only thing with the version I'm thinking that might be breaking is that we're enforcing rgeo 3. I'm not sure about best practices for when there's a big dependency upgrade like that, but since this gem is usually just used downstream of an adapter and not independently installed a major change is ok since the postgis adapter is about to undergo a major change too.

[keithdoggett]

Thanks @tagliala

[tagliala]

Welcome. I didn't check if there is dead code, now that 2.0 and 1.0 have been dropped. I'm not familiar with RGeo internals