chore: pin version of commons dependency #3880
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes
This PR updates the
package.json
for all utilities that depend on thecommons
package so that they now require the same version of the package as their own.Since we version all our utilities together, this ensures that whenever there's an update to
commons
that updated version is installed with the correct version of each utility. Prior to this fix, the version range used the^
symbol, which meant that depending on how customers updated a utility (i.e.logger
) npm might not have updatedcommons
in case of a minor version update.The change should be seamless and not require any change on the customer side, since it'll be effective starting from the next release.
Issue number: fixes #3879
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.