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.

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

Support beta/canary version number format #12

Merged
merged 2 commits into from
Dec 15, 2015

Conversation

minichate
Copy link
Contributor

We should support beta and canary version formats in the form of 2.3.0-beta.2+41030996, since tools like ember try:testall will attempt to pull down prerelease versions that don't (yet) have strictly semver compatible numbers.

We should support beta and canary version formats in the form of
`2.3.0-beta.2+41030996`, since tools like `ember try:testall` will
attempt to pull down prerelease versions that don't yet have strictly
semver compatible numbers.
@rwjblue
Copy link
Member

rwjblue commented Dec 15, 2015

I want the version to match what is actually being used. The issue is mostly that the semver package does not consider prereleases to satisfy a non-prerelease range.

We can fix the isAbove helper to use gt instead of satisfies, but I'm not sure if the upstream lib you are using uses isAbove or something else.

@rwjblue
Copy link
Member

rwjblue commented Dec 15, 2015

Also, that version number listed in the description is a semver compliant version number (but it may not match when using "semver.satisfies(this.version, '> 1.13.0')").

@minichate
Copy link
Contributor Author

The check the upstream app is trying to do is:

checker.for('ember', 'bower').assertAbove('1.13.7');

so changing .isAbove to defer to semver.gt should work. I'll see if I can adjust this PR.

@rwjblue
Copy link
Member

rwjblue commented Dec 15, 2015

👍

rwjblue added a commit that referenced this pull request Dec 15, 2015
Support beta/canary version number format
@rwjblue rwjblue merged commit 0c70501 into ember-cli:master Dec 15, 2015
@rwjblue
Copy link
Member

rwjblue commented Dec 15, 2015

Released as v1.1.5.

@rwjblue rwjblue added the bug label Jan 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants