![]() If we are going to use semantic-release in an existing repository we'll first have to make sure that the most recent commit included in the last published npm release is in the release branches history and is tagged with the version released. ![]() It automatically sets the next semantic version number, generates the changelog and publishes the release. Semantic-release is a tool that uses the Conventional Commits message format to determine the type of changes in our code base. It uses YAML files, called workflows, that trigger based on specific events (e.g. You can think of it as the CI/CD pipeline for GitHub. GitHub Actions is a GitHub feature that lets us build, test, and deploy our GitHub hosted projects. ![]() GitHub Actions and semantic-release have us covered! Wouldn't be great if we could automate all of these tasks? Execute any build steps to create the release artifacts.Create a new Git tag and a GitHub release.Change the version field in package.json.When we are developing JavaScript packages, there is a series of repetitive tasks that we have to complete manually every time we have to publish a new release to npm:
0 Comments
Leave a Reply. |