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
Is your feature request related to a problem? Please describe.
Not a problem
Describe the solution you'd like
I would like to have meaningful version when deploying to prod
The prod deployment should check if it is a patch, minor or major release and automatically increase the version number in the GIT repo.
Check https://docs.npmjs.com/about-semantic-versioning for further information
Describe alternatives you've considered
Using JIRA Ticket numer could be an option but does not indicate the version itself
Additional context
A file CHANGELOG.md should also be created after deployment.
The process should be as follows:
Try to build
If build succeeded, bump version according to type of deployment (patch, minor, release)
Create CHANGELOG.md
Tag current version with version number
commit and push changes to version, tag and CHANGELOG.md
The version could be tracked in a package.json as it commonly used in several open source projects
The text was updated successfully, but these errors were encountered:
culmat
changed the title
[FEATURE] Semantic versioning on prod deployment and CHANGELOG creation
Semantic versioning on prod deployment and CHANGELOG creation
Oct 19, 2020
Is your feature request related to a problem? Please describe.
Not a problem
Describe the solution you'd like
I would like to have meaningful version when deploying to prod
The prod deployment should check if it is a patch, minor or major release and automatically increase the version number in the GIT repo.
Check https://docs.npmjs.com/about-semantic-versioning for further information
Describe alternatives you've considered
Using JIRA Ticket numer could be an option but does not indicate the version itself
Additional context
A file CHANGELOG.md should also be created after deployment.
The process should be as follows:
The version could be tracked in a package.json as it commonly used in several open source projects
The text was updated successfully, but these errors were encountered: