chore: re-enable using current pkg versions for api compat checks #8427
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.
This was originally added in commit
3dd21b9.
However, the script fails during a bump build when the package version
in lerna.json is ahead of the latest published in NPM. This was worked
around by turning this feature off -
09a1f33.
Re-enable this feature and handle version in lerna.json may be ahead of
NPM.
Testing
Manually tested three cases -
lerna.json
is <= package published in NPMlerna.json
is > package published in NPMDOWNLOAD_LATEST
is set totrue
.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license