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

Using grunt-bump as a pre-deploy hook causes jitsu to see previous verison number #434

Open
joeybaker opened this issue Apr 4, 2013 · 3 comments

Comments

@joeybaker
Copy link

I've got a grunt task set as a "predeploy" hook in package.json, one of the tasks is to bump the version number, but it seems like jitsu isn't capturing that change. Example output:

Running "bump:patch" (bump) task
bump: bumping file "package.json"...0.0.4 -> 0.0.5
bump: bumping file "component.json"...0.0.4 -> 0.0.5

Done, without errors.
info:    Creating snapshot 0.0.4
info     Uploading: [=============================] 100%
@booyaa
Copy link

booyaa commented May 23, 2013

can you include your Gruntfile.js? i'd like to test as i also use grunt. i know by default jitsu will bump the version in package.json after each deploy. i've not tested it if you already have a numbering scheme in place.

@joeybaker
Copy link
Author

Sure thing, you can take a look here: https://github.com/joeybaker/wheelhouse/blob/master/Gruntfile.js

@joeybaker
Copy link
Author

@booyaa just checking in – have had the time to look at this?

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

2 participants