Skip to content
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

Avoid downgrading release-it / release-it-lerna-changelog. #36

Merged
merged 2 commits into from
Mar 17, 2020

Conversation

rwjblue
Copy link
Owner

@rwjblue rwjblue commented Mar 17, 2020

When the project that we are runnign against has a newer version of release-it or release-it-lerna-changelog we would always downgrade their specified version to whatever we have specified in our own devDependencies.

This is pretty bad behavior, and has been fixed. Now if the project defines a dev dependency that is newer than our range, we use it directly.

When the project that we are runnign against has a newer version of
`release-it` or `release-it-lerna-changelog` we would always downgrade
their specified version to whatever we have specified in our own
`devDependencies`.

This is pretty bad behavior, and has been fixed. Now if the project
defines a dev dependency that is _newer_ than our range, we use it
directly.
@rwjblue rwjblue added the bug Something isn't working label Mar 17, 2020
@rwjblue rwjblue merged commit f96e6d4 into master Mar 17, 2020
@rwjblue rwjblue deleted the preserve-existing-devDep-versions branch March 17, 2020 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant