Skip to content

Semantic versioning on prod deployment and CHANGELOG creation #4

@whvneo

Description

@whvneo

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:

  1. Try to build
  2. If build succeeded, bump version according to type of deployment (patch, minor, release)
  3. Create CHANGELOG.md
  4. Tag current version with version number
  5. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions