Colby Fayock: 0:00 We're going to start off with a new custom Action in GitHub. When using Actions in your workflow, you want to make sure you are using a tag. This way, you can specify the exact version that you're using for your project.
0:09 Inside our project, we're specifying our version, but we are not adding tags. inaudible want to use the Git Tag functionality. This is inaudible right into Git. Alternatively, we can use npm-version. This feature from npm will both update the version of your package and add a tag.
0:23 To do that, we're going to start off by adding an npm script called bump. Here we simply get to run the command npm version. Really, you don't need bump and can instead use npm. We're adding bump just to make it a little bit easier.
0:35 By default, running npm version just shows the version information of our environment. Instead, we want to use it to bump up the version.
0:41 Npm uses semantic versioning. This means we have a few different options for what we want to upgrade. In our case, let's make this 1..1. In order to bump just that last number, we're going to use patch. Let's run yarn bump patch. Once it's finished, we can see the new version.
0:56 If you notice, in your package.json file you'll also see that the version there is incremented. Part of the goal is to get a tag. If we run git tag, we can now see our version. Once we push that to GitHub, we can see our new package version. We can also see that we have a new tag. Now that we have our new tag, when we reference our Action externally, we can add a tag just like actions/checkout.
1:16 In review, we wanted to add versioning and tagging to our Action. Inside our package.json we added a bump script that ran npm version. Once we ran that script with patch, we saw our version increment and we saw our new tag on our project.