Conversation
|
It looks like this PR is missing a label to determine the type of change it introduces. The maintainer should add one of the following labels:
Additionally, the maintainer may also want to add one of the following:
Once the correct labels have been set, simply remove the |
kennyadsl
left a comment
There was a problem hiding this comment.
I have a PR ready that fixes specs. That PR will probably need a major bump but I'm not sure yet it's the right thing to do but if that's the case probably we can release this change along with the major bump.
572fb4b to
22c60b1
Compare
|
@kennyadsl Any reason we can't merge this so we can get tests running at least against older versions of Solidus and work on getting tests passing against |
|
I think we can move this forward now @waiting-for-dev, isn't it? |
22c60b1 to
e9b8f72
Compare
Ref. solidusio/solidus#5042 [skip ci]
e9b8f72 to
b580bd8
Compare
b580bd8 to
14a0ba8
Compare
|
Done! Please, let us know if there's any problem. |
…us_main Adapt to new Solidus default branch name
Summary
Stop trying to pull solidus_frontend v4, which doesn't exist.
Adopt new Solidus default branch. Ref. solidusio/solidus#5042
Checklist
Check out our PR guidelines for more details.
The following are mandatory for all PRs:
The following are not always needed: