Capistrano should cleanup bundled gems for old ruby versions #149
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.
Deletes shared bundle files that no longer match any installed releases. For example, if the currently installed releases are all ruby 3.2 and 3.3., this will remove any installed ruby 3.1 gems.
For deployments with long-lived application servers, this limits the space growth of application deployments. There isn't anything yet to remove installed
.rbenvversions: this is harder, because multiple deployments can share the same user account – possibly inside nested directories.Capistrano:
deploy:preinstallshould fix up installed gem permissions. (Before this fix,deploy:preinstallwould abort before fixing up gem permissions.)Support Ruby 3.4.