-
Notifications
You must be signed in to change notification settings - Fork 36
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
feature request: also bump deps in package distribution folder #105
Labels
Comments
🎉 This issue has been resolved in version 2.12.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 in
B
'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 the
package.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!
The text was updated successfully, but these errors were encountered: