Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

upgrade to newer semver, fixes #1817,#1845,#1851 #1852

Merged
merged 1 commit into from
Jul 28, 2015
Merged

upgrade to newer semver, fixes #1817,#1845,#1851 #1852

merged 1 commit into from
Jul 28, 2015

Commits on Jul 23, 2015

  1. upgrade to newer semver, fixes bower#1817,bower#1845,bower#1851 

    Upgrading to latest version of semver to fix (bower#1817, bower#1845, bower#1851).

Possible breaking changes in regards to the way semvers handles pre-releases.

If a version has a prerelease tags (for example, 1.2.3-alpha.3) then it will only be allowed to satisfy comparator sets if at least one comparator with the same [major, minor, patch] tuple also has a prerelease tag.

For example, the range >1.2.3-alpha.0 would be allowed to match the version 1.2.3-alpha.7, but it would not be satisfied by * or 1.2.3. See [semvers](https://github.com/npm/node-semver#prerelease-tags) additional details.
    @peterkc
    peterkc committed Jul 23, 2015
    Configuration menu
    Copy the full SHA
    8744449 View commit details
    Browse the repository at this point in the history