root
└── dist
├── A
└── B
└── projects
├── A
└── B (depends on A)
When releasing both A and B, MSR will eventually find that A needs to be updated in B's deps.
It will even include a note for that in B's release notes: "Dependencies A: upgraded to x.x.x".
Which is a great feature!
But in my case both A and B where built to a dist folder prior to running MSR.
And the package.json that MSR will actually updates (in updateDeps.js#L311) is projects/B/package.json not dist/B/package.json which is the one that needs to be updated before publishing.
Would it be possible to also look for the pkgRoot option of @semantic-release/npm and made the changes in there too ?
Consider the following:
When releasing both
A
andB
, MSR will eventually find thatA
needs to be updated inB
's deps. It will even include a note for that inB
's release notes: "Dependencies A: upgraded to x.x.x". Which is a great feature!But in my case both
A
andB
where built to adist
folder prior to running MSR. And thepackage.json
that MSR will actually updates (in updateDeps.js#L311) isprojects/B/package.json
notdist/B/package.json
which is the one that needs to be updated before publishing.Would it be possible to also look for the
pkgRoot
option of@semantic-release/npm
and made the changes in there too ?Thanks!