Improve CI workflow

[tagliala]

• Update checkout action to v3. Node.js 12 actions are deprecated
• Test against Ruby 3.2
• Test against Ruby and Rails head to detect breaking changes and deprecation
  in advantage. Mark runs as experimental, so they are allowed to fail

---

@adzap thanks for the release

There is a suggestion on the CI workflow, but if you prefer I can split the experimental checks and schedule them weekly or something like that

[tagliala]

Updated with latest RubyGems and Ruby 3.2

[tagliala]

Updated to test against Rails 7.1 stable

/cc @adzap

[tagliala]

Test against Ruby 3.3 stable

[tagliala]

Need to bisect rails-edge.

Failures depends by #241 , fixed in #242

[tagliala]

Reson for closing:

I've eventually moved to the built-in comparison validator

Relevant changes:

diowa/icare@dd4a467#diff-8f06df7d19040b42d0ab94249895f10fac375834ce5a6f4e55b93570b9dd7d8fL26-R27

[diogonoda]

hi @tagliala !!!
First of all, thanks for contributing with the project!

There's one feature that I couldn't find in Rails which is the validation on the date type.
For example, if I need to validate an attribute that could be nil:
validates_date :my_date_attribute, allow_blank: true

since Rails will just set my_date_attribute to nil if I try assigning it with String, using validate_timeliness is still valuable to me.
Indeed, Rails comparison will replace some of the features provided by the gem, but not all of them.
That said, I don't see the reason for the EOD of this gem.

Am I missing something here?

[tagliala]

That said, I don't see the reason for the EOD of this gem.

It is unmaintained, and the built-in rails validator is ok for most of the use cases

PS: didn't understand the use case, did you check allow_nil ?