Update bundler to v2.4.18 as this is what we use in staging/production #3266
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Neil mentioned he was getting the following error:
There was an error installing the locked bundler version (2.3.12), rerun with the
--verboseflag for more details. Going on using bundler 2.4.18.
It appears Jupiter has been using v2.3.12 for over a year now (This was last updated here: d1071c3)
This issue is staging/production are on v2.4.18 of bundler now. We not sure why these versions are different.
So let's update Jupiter to use v2.4.18 so everything is on the same version going forward.
(NOTE: None of our projects are using this version. Doing a search in our organization, the only reference I see to this version was our last release, so perhaps it got updated in v2.5.2: https://github.com/ualbertalib/Unix/blob/f57eb7c280c6a8fea7d228e260e9c5063cdf6ecd/Change/2023/Q3/CR00001145.html#L357).