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

use valid semver range for engine #81

Merged
merged 1 commit into from
Jul 23, 2015
Merged

use valid semver range for engine #81

merged 1 commit into from
Jul 23, 2015

Conversation

silverwind
Copy link
Contributor

yocontra pushed a commit that referenced this pull request Jul 23, 2015
Merge pull request #81 from silverwind/patch-1
c7887c1 
use valid semver range for `engine`
@yocontra yocontra merged commit c7887c1 into gulpjs:master Jul 23, 2015
@phated
Copy link
Member

phated commented Jul 23, 2015

For posterity. Isaac said this won't match prerelease versions still...

@silverwind
Copy link
Contributor Author

Yeah, the issue turned out to be strictEngine related and the space actually isn't significant. Won't hurt I guess :)

phated pushed a commit that referenced this pull request Dec 5, 2017
@yocontra
Merge pull request #81 from silverwind/patch-1
1e7434e 
use valid semver range for `engine`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@silverwind @phated @yocontra