{"id":323503,"date":"2020-11-02T09:02:40","date_gmt":"2020-11-02T16:02:40","guid":{"rendered":"https:\/\/css-tricks.com\/?p=323503"},"modified":"2020-11-02T09:21:20","modified_gmt":"2020-11-02T16:21:20","slug":"how-to-automate-project-versioning-and-releases-with-continuous-deployment","status":"publish","type":"post","link":"https:\/\/css-tricks.com\/how-to-automate-project-versioning-and-releases-with-continuous-deployment\/","title":{"rendered":"How to Automate Project Versioning and Releases with Continuous Deployment"},"content":{"rendered":"\n

Having a semantically versioned<\/a> software will help you easily maintain and communicate changes in your software. Doing this is not easy. Even after manually merging the PR, tagging the commit, and pushing the release, you still have to write release notes. There are a lot of different steps, and many are repetitive and take time.<\/p>\n\n\n\n

Let\u2019s look at how we can make a more efficient flow and completely automating our release process<\/strong> by plugin semantic versioning into a continuous deployment process.<\/p>\n\n\n\n\n\n\n

Semantic versioning<\/h3>\n\n\n

A semantic version is a number that consists of three numbers separated by a period. For example, 1.4.10<\/code> is a semantic version. Each of the numbers has a specific meaning.<\/p>\n\n\n\n