-
Notifications
You must be signed in to change notification settings - Fork 936
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Best Practice For Importing Another Bit Component to Avoid Ripple CI Failure #8793
Comments
can you run |
This is what I see (and the
|
I am still battling with this. Every time I end up bumping the version of my
And I get an error trying to update components in my apps:
|
Are you running install directly with |
Bit install with yarn configured |
Also, I am now running bit version 1.7.41, yarn 4.3.1 (still on node 21.4.0). |
Description
Ripple CI fails when I import another of my Bit components when the underlying Bit component's version has been bumped.
Specifications
Context and additional information
I have a library in Bit in which several components are built on others. Lately I have been experiencing Ripple CI build failures when importing another of my Bit components:
I get Ripple CI build errors when I tag all of the updated components and
bit export
them:But
@severed-links/common.js
does exist with that semver number:I feel like I am doing something very dumb and I hesitated even raising the issue to bother you all, but I just can't figure out why I am getting these build errors simply trying to use another of my components.
The text was updated successfully, but these errors were encountered: