Fix CI on Solidus v3.1 by explicitly fetching solidus_frontend from GH #241
Conversation
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
kennyadsl
approved these changes
Feb 14, 2023
Member
kennyadsl
left a comment
kennyadsl
left a comment
There was a problem hiding this comment.
Thanks for taking care of this Marc!
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.
Summary
This is the same fix that was used in 9f1f60b. Otherwise, bundler will try to fetch the gem from RubyGems and complain because not finding
v3.1.10.devversion.Closes #239
Checklist
Check out our PR guidelines for more details.
The following are mandatory for all PRs:
The following are not always needed: