You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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?
@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?
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).
The text was updated successfully, but these errors were encountered: