Skip to content
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

Update to ruby 3.3 completely #4320

Merged
merged 1 commit into from Jan 1, 2024
Merged

Conversation

segiddins
Copy link
Member

No description provided.

Copy link

codecov bot commented Dec 29, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (47cef0d) 98.73% compared to head (eee521d) 98.73%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4320      +/-   ##
==========================================
- Coverage   98.73%   98.73%   -0.01%     
==========================================
  Files         336      336              
  Lines        7415     7414       -1     
==========================================
- Hits         7321     7320       -1     
  Misses         94       94              

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

Dockerfile Show resolved Hide resolved
@segiddins segiddins merged commit 9073050 into master Jan 1, 2024
15 of 16 checks passed
@segiddins segiddins deleted the segiddins/update-to-ruby-3.3 branch January 1, 2024 06:10
@@ -25,11 +25,7 @@ ENV BUNDLE_APP_CONFIG=".bundle_app_config"

# Update rubygems
ARG RUBYGEMS_VERSION
RUN gem update --system ${RUBYGEMS_VERSION} --no-document && \
# rubygems-update is completely unused after the `gem update --system` process
gem uninstall rubygems-update -x && \
Copy link
Member

Choose a reason for hiding this comment

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

Interesting! I think the comment above is still true, and I would expect gem uninstall rubygems-update -x to still work. I was actually considering recently that this should be the default behavior and no rubygems-update gem should be left around. Maybe some rubygems regression?

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.

None yet

3 participants