I'm not quite sure if I understand your question completely. The tool should not be used to trigger a CI pipeline. The idea behind node-publisher was to prevent

I'm not quite sure if I understand your question completely. The tool should not be used to trigger a CI pipeline. The idea behind node-publisher was to prevent broken packages being published. A CI helps us in the prevention of these errors before a branch is merged into master. Node-publisher helps with the last mile in those cases where the publishing itself is more complicated than just calling `yarn publish patch` or similar.