chore: fix versions in package.json
#281
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.
Dependencies on packages in monorepo should always be
^0.0.0
. They will be changed into exact dependency versions, if necessary, at release time.Due to some previous attempts at implementing that workflow, some literal
"0.0.0"
's had snuck into ourpackage.json
s, andprojen
leaves them at whatever they are.Now that we are explicitly setting versions back to
^0.0.0
atunbump
time, that causes a diff with respect to the literal exact versions that are in the repo.Manually set them to caret versions.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license