Closed antongolub closed 4 years ago
The first package have no commits requiring release, but the second depends on the first. So, this is not a tool issue. builds/174295307
this is a cryptic error, why should the process fail?
@yyynnn
Hi.
It seems that if we skip this a check, we will publish a package that cannot be installed because its dependency is not yet present in the registry. No tag > no release > no package
// Loop through localDeps to update dependencies/devDependencies/peerDependencies in manifest.
pkg._localDeps.forEach((d) => {
// Get version of dependency.
const release = d._nextRelease || d._lastRelease;
// Cannot establish version.
if (!release || !release.version)
throw Error(`Cannot release because dependency ${d.name} has not been released`);
travis#174292182