The Angular DevOps Series: Semantically release your Angular library

Are you, like me, getting tired of releasing your Angular library manually? And how about keeping that CHANGELOG up to date? In this post I’m taking you along in my journey towards a fully automated process for my ngx-testing-library library!

The Angular DevOps Series

This post is the first post of the Angular DevOps Series. The series will also include another post by fellow Angular in Depth writer, Todd Palmer, who will walk you through the details of deploying an Angular application with Travis CI to GitHub pages.

Introduction

As a bit of background, ngx-testing-library is created with the ng generate library command and has tests written in the library as well as tests in the example application using it. To build and test my changes, I’m already using CircleCI as my Continuous Integration (CI) server.

Before we start let’s make a list of what we’re trying to accomplish after we push a commit:

🔲 Only release when the build passes
🔲 Only release when the push has been made to the master branch
🔲 Release the new version to npm
🔲 Release the new version to GitHub
🔲 Keep the CHANGELOG up to date️