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

No bumping #110

Open
Raynes opened this issue Feb 23, 2015 · 2 comments
Open

No bumping #110

Raynes opened this issue Feb 23, 2015 · 2 comments

Comments

@Raynes
Copy link

Raynes commented Feb 23, 2015

It'd be nice if we could specify --no-bump to prevent a bump from happening. For example, for your first release. If you've already committed a scaffolding-generated package.json file you probably already have a version like 0.1.0 or something. I don't see a way to get around that without committing the file with version '0.0.0' to start with.

Thoughts on the best way to solve this? I'd happily submit some a PQ, just want to make sure we're on the same page before I go doing work that might not be accepted!

@sholladay
Copy link

+1 ... configure all the things

@Kjir
Copy link

Kjir commented Oct 16, 2015

If you don't have a tag with that name, I think you could work around this by specifying the exact version: grunt release:0.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants