Skip to content
This repository has been archived by the owner on Aug 5, 2022. It is now read-only.

What if the version in package.json has a prefix like v1.6.1? #61

Closed
ahmed-abdulmoniem opened this issue Oct 28, 2016 · 3 comments
Closed

What if the version in package.json has a prefix like v1.6.1? #61

ahmed-abdulmoniem opened this issue Oct 28, 2016 · 3 comments

Comments

@ahmed-abdulmoniem
Copy link

Hi guys,

What if the version in package.json has a prefix like v1.6.1?

When I try the gulp-bump it says that this is invalid semver .. but actually it is so important to support prefixes?

Any workaround?

Thanks.
@ahmed-abdulmoniem
Copy link
Author

any clue?

@stephenlacy stephenlacy mentioned this issue Oct 30, 2016
Closed
stephenlacy added a commit that referenced this issue Oct 30, 2016
@stephenlacy
Update dependencies to add features for #60 and #61
7fe2945
@stephenlacy
Copy link
Owner

I happen to be the only maintainer of this project and am not madly programming every single weekend, as such "I have a life". Please be respectful as I (or the community) will answer in due time.

I have added support for modifying versions with a prefix, available in published version 2.5.0

@ahmed-abdulmoniem
Copy link
Author

@stevelacy Respectful!!!!!! What I have said that makes you so angry!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stephenlacy @ahmed-abdulmoniem