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.
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.
I'm cautious to make changes to the v1 plugin itself, due to the fact that it's been stable for a long time and that I don't know much about Ruby.
I am considering updating the documentation to mention the
BUNDLE_GEMFILE
environment variable. Or it could become a parameter in the snapcraft.yaml (i.e.ruby-gemfile-location: <path-to-gemfile>
).Aside: Ruby
2.6
is EOL and the latest supported release is3.2
. Not sure if/when it's appropriate to update the default Ruby version.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.
For now I think this is a good minimal change to get this spread test fixed. However, if it works on Ruby 2.7 that'd probably be reasonable since it should be fully backwards compatible.
In theory Ruby 3 is backwards compatible too, but we should probably make a separate project for bringing our ruby deps up to the latest.