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

Add a version number #22

Open
oschneid opened this issue Jan 28, 2016 · 2 comments
Open

Add a version number #22

oschneid opened this issue Jan 28, 2016 · 2 comments
Assignees

Comments

@oschneid
Copy link
Collaborator

This should be available in a build specification, and accessible in an "About" menu item that describes Macaron and gives the version number (preferably auto generated from the one setting).

@hasumonn
Copy link
Contributor

Version number is now put next to the title, and can be incremented when running deploy script.

As we are using Semantic Versioning, we need to specify if the update is major, minor or patch when deploy by running one of the following:
npm run deploy-major
npm run deploy-minor
npm run deploy-patch

Instead of writing version number to another file, I added a version field to package.json. Because in that way, we can use npm's bump-version to increment the version number. I'm not sure if it will be better to write it in another file?

@oschneid
Copy link
Collaborator Author

@ryanbom I'm running into a problem when trying to build -> what new packages did you need to install to get nom-bump to work? Can you use --save-dev to re-install them and push that version so I can make sure to install the same packages?

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