github/workflows in the root of your repository. If you haven't already, create the directories. Learn to simplify day-to-day code and the balance between over- and under-engineering. Build the project and run tests to make sure everything works.Update the version in package.json based on the release tag.In the build, first, check out the branch the release is targetting.When publishing a release, trigger a workflow.I want to be able to publish, of course, the current version, but also version 1 in case a patch is needed.Īnd here's what I need the pipeline to do: The reason for these branch names will become apparent later. The code for version 1 is on the branch v1-latest. The code for this (the latest version) is on the branch latest. For example, we could publish when pushing to a certain branch, creating a tag, creating a commit in a specific pattern, or by creating a release on GitHub directly.įor my project flooent, I went with the last option. There are a couple of ways we can set up publishing to NPM. Now that we are all done with CI, let's tackle CD.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |