[Meteor 3] Fix how to compare constraints version when publishing a package #13082
+14
−2
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.
We had reports that people weren't able to deploy packages because they were getting the error:
Debugging further, I could check that here,
d.constraint
anduse.constraint
were never equal if usingapi.versionsFrom
with conditioning versions for a package, like'mongo@1.6.9||2.0.0-beta300.7'
.What I'm doing on this PR is to verify if the package constraint version is available in the specified Meteor version determined by
api.versionsFrom
.