-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Make lockfile platforms easier to maintain #8344
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #8344 +/- ##
=======================================
Coverage 99.10% 99.10%
=======================================
Files 140 140
Lines 4018 4018
=======================================
Hits 3982 3982
Misses 36 36 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you know where the *-21
and other platform values come from (how they get added/removed) or if Bundler has docs that cover these?
Do you want to make the same changes to the lock files in the /gemfiles
directory too?
Yeah, I should've added a bit more context! So these platform values ultimately come from Ruby. For example,
When Bundler is run, it uses the value of the local platform, and finds the optimal resolution for the local platform. For example, if you're on The specific number in this case is supposed to track the specific macOS version. However, in practice, gem authors don't release macOS version specific variants of their gems, since the platforms are the same in practice. So, there's no Recent versions of Bundler will "optimize" this, and as long as no variants specific to the macOS version exist, it will lock only arch + OS, but not the specific macOS version. So, these should not get added in the future again as long as we use a recent enough version of Bundler. I'll add the same changes to the other gemfiles, good idea! |
395414a
to
86be771
Compare
Oh great, just tested because my dev environment was adding platforms and it does not happen on this branch |
There was a problem hiding this comment. 10000
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
86be771
to
8722101
Compare
Thanks both! |
This should work equally well and has less churn when maintainers upgrade their OS or switch platforms. Recent versions of Bundler will "optimize" this, and as long as no variants specific to the macOS version exist, it will lock only arch + OS, but not the specific macOS version. These should not get added in the future again as long as we use a recent enough version of Bundler, and for this reason locked Bundler has been bumped to 2.5.11 Ref: activeadmin/activeadmin#8344
This should work equally well and has less churn when maintainers upgrade their OS or switch platforms. Recent versions of Bundler will "optimize" this, and as long as no variants specific to the macOS version exist, it will lock only arch + OS, but not the specific macOS version. These should not get added in the future again as long as we use a recent enough version of Bundler, and for this reason locked Bundler has been bumped to 2.5.11 Ref: activeadmin/activeadmin#8344
This should work equally well and has less churn when maintainers upgrade their OS or switch platforms. Recent versions of Bundler will "optimize" this, and as long as no variants specific to the macOS version exist, it will lock only arch + OS, but not the specific macOS version. These should not get added in the future again as long as we use a recent enough version of Bundler, and for this reason locked Bundler has been bumped to 2.5.11 Ref: activeadmin/activeadmin#8344
Also backport activeadmin#8344
Also backport activeadmin#8344 and use latest rubygems from activeadmin#8370
Also: - Backport activeadmin#8344 - Use latest rubygems (partial backport of activeadmin#8370) - Backport activeadmin#8372
- Test against Rails 7.2 - Test against Ruby 3.3 - Make lockfile platforms easier to maintain (ref: activeadmin/activeadmin#8344) - Update bundles
- Test against Rails 7.2 - Test against Ruby 3.3 - Make lockfile platforms easier to maintain (ref: activeadmin/activeadmin#8344) - Update bundles by using the minimum supported ruby version
- Test against Rails 7.2 - Test against Ruby 3.3 - Make lockfile platforms easier to maintain (ref: activeadmin/activeadmin#8344) - Update bundles by using the minimum supported ruby version
- Test against Rails 7.2 - Test against Ruby 3.3 - Make lockfile platforms easier to maintain (ref: activeadmin/activeadmin#8344) - Update bundles by using the minimum supported ruby version
- Test against Rails 7.2 - Test against Ruby 3.3 - Make lockfile platforms easier to maintain (ref: activeadmin/activeadmin#8344) - Update bundles by using the minimum supported ruby version
- Test against Rails 7.2 - Test against Ruby 3.3 - Make lockfile platforms easier to maintain (ref: activeadmin/activeadmin#8344) - Update bundles by using the minimum supported ruby version
- Test against Rails 7.2 - Test against Ruby 3.3 - Make lockfile platforms easier to maintain (ref: activeadmin/activeadmin#8344) - Update bundles by using the minimum supported ruby version
This should work equally well and has less churn when maintainers upgrade their OS or switch platforms.