Skip to content

Minor development updates #8488

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from

Conversation

tagliala
Copy link
Contributor

@tagliala tagliala commented Sep 27, 2024

  • Update dependencies
  • Improve test app generator
  • Test Rails 7.0 (instead of 7.1) against Ruby 3.0

@tagliala tagliala marked this pull request as draft September 27, 2024 13:43
@tagliala
Copy link
Contributor Author

https://github.com/activeadmin/activeadmin/actions/runs/11071311136/job/30762881938#step:5:1278

sqlite3-2.1.0-x86_64-linux-gnu requires ruby version < 3.4.dev, >= 3.1, which is
incompatible with the current version, 3.0.7

This is unfortunate

@@ -32,7 +32,7 @@ jobs:
include:
- ruby: '3.0'
os: ubuntu-latest
rails: rails_71
rails: rails_70
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this solution to #8488 (comment) is acceptable, I will change the required actions in settings to allow the branch to be merged without skipping branch rules

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with dropping Ruby 3.0 from CI now. If that helps here and you are ok with it, let's do that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would not do that if 3.0 is supported, I'm afraid of unintended breaking changes at patch level, in example by using 3.1 only syntax (like Array#intersect?)

This happened several times in the past, a couple of the most recent breaking changes at patch level that I remember are

Please let me know what you think

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well I figure we would bump the minimum required version anyway. I recall we've done that each time we've dropped an old EOL version. You are welcome to open that PR to drop Ruby 3.0 now if you want.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As a reference, here it is another breaking change introduced in a patch level release because of the shorthand syntax (>= 3.1)

rails/importmap-rails#268

Copy link

codecov bot commented Sep 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.11%. Comparing base (3b54bde) to head (18d8fcf).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #8488   +/-   ##
=======================================
  Coverage   99.11%   99.11%           
=======================================
  Files         141      141           
  Lines        4069     4069           
=======================================
  Hits         4033     4033           
  Misses         36       36           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

- Sort skips
- Skip `rubocop`, `brakeman`, and `ci`
Will test the minimum required Ruby version against the minimum required
Rails version to allow Rails 7.1 to use sqlite 2.1

```
sqlite3-2.1.0-x86_64-linux-gnu requires ruby version < 3.4.dev, >= 3.1, which is
incompatible with the current version, 3.0.7
```
@tagliala tagliala marked this pull request as ready for review September 27, 2024 14:17
@tagliala
Copy link
Contributor Author

Superseded by #8489

@tagliala tagliala closed this Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants