Repository navigation
Delay default path and global cache changes to Bundler 5 - #8867
Merged
deivid-rodriguez merged 3 commits intoJul 25, 2025
Merged
deivid-rodriguez merged 3 commits into
deivid-rodriguez merged 3 commits into
Conversation
We now run specs against a single version, so I prefer to keep a single branch. Once we bump the major version, this will need very little updates, and that seems fine.
There are several issues with these which I'm not sure I'll have time to address properly. I prefer to keep our default branch in a releasable state just in case. Once they are fixed, this can be reverted.
deivid-rodriguez
force-pushed
the
deivid-rodriguez/delay-path-changes-and-global-cache
branch
from
July 25, 2025 09:34
4be09f5 to
c314d7b
Compare
deivid-rodriguez
marked this pull request as ready for review
July 25, 2025 11:30
indirect
approved these changes
Jul 25, 2025
indirect
left a comment
indirect
left a comment
There was a problem hiding this comment.
The delay is a bummer but I am fully onboard with keeping things releasable while the issues are worked through 👍🏻
deivid-rodriguez
deleted the
deivid-rodriguez/delay-path-changes-and-global-cache
branch
July 25, 2025 17:02
4 tasks done
deivid-rodriguez
added a commit
that referenced
this pull request
Sep 4, 2025
…anges-and-global-cache Delay default path and global cache changes to Bundler 5 (cherry picked from commit 20b093f)
deivid-rodriguez
added a commit
that referenced
this pull request
Sep 9, 2025
…anges-and-global-cache Delay default path and global cache changes to Bundler 5 (cherry picked from commit 20b093f)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What was the end-user or developer problem that led to this PR?
Main issues people are finding with Bundler 4 are related to these changes in defaults. In particular, the new global cache of compiled extensions is creating several problems. I'm still thinking about how to address those issues, but I want to keep our main branch in a releasable state without outstanding blockers in the mean time.
What is your fix for the problem, implemented in this PR?
Delay global cache changes to Bundler 5. Since global cache changes are a prerrequiste for changing the default to install to a local
.bundlefolder by default, since that's what prevents degrading default performance ofbundle installdue to extension recompilation, delay that change too.Make sure the following tasks are checked