-
Notifications
You must be signed in to change notification settings - Fork 219
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
[issue] When publishing, an error from one package breaks the call to create a tag for all the others #218
Comments
That is true - but it's also a little bit complicated to fix. Should |
@Andarist It would be cool if the packages were published one by one, taking into account the dependencies among themselves, but in this case, this is not important. Consider that packages do not depend on each other in this case. |
Well, this case is important for designing how it should work. I agree that this is overall a problem worth solving but to do that we need to consider all the possible situations. |
@Andarist I think that everything should start with the fact that need a function to calculate the dependency tree. This exists, for example, in (nx affected. |
for example
2 packages should be published:
package A
package B
If for some reason the
package A
fails to publish to npm, but thepackage B
publishes successfully, then the git tag and github release for thepackage B
will not be generated.The text was updated successfully, but these errors were encountered: