We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This tool can traverse recursively your linked projects.
With this in mind we could use recursively a combination of:
The first command is helpful to map outdated dependencies and check which is the last minor backward compatible version.
With the second command we can update the package.json to that minor version and keep the ^ range.
By doing this, we can have a repo tree synced to latest minor version and avoid build inconsistencies.
The next output of the first command should evidence only the major releases that could potentially break retro compatibility.
The text was updated successfully, but these errors were encountered:
Fix the ">" string comparison on versions because "2.5.6" > "2.5.10", and the dependency is not being upgraded.
We should make a split on "." and compare major, minor, patch directly.
Sorry, something went wrong.
No branches or pull requests
This tool can traverse recursively your linked projects.
With this in mind we could use recursively a combination of:
The first command is helpful to map outdated dependencies and check which is the last minor backward compatible version.
With the second command we can update the package.json to that minor version and keep the ^ range.
By doing this, we can have a repo tree synced to latest minor version and avoid build inconsistencies.
The next output of the first command should evidence only the major releases that could potentially break retro compatibility.
The text was updated successfully, but these errors were encountered: