00:00 So when it comes to releasing the packages, now normally you just push them to some registry like npm. But it's also the concept of releasing it on GitHub. And that is usually a combination of changelogs as well. So if we go for instance here to the NX repo, which I'm picking here as an example, they

00:17 release it also on GitHub and not just to npm. So if you go to that releases tab on GitHub, you can see the releases being listed in here. And if you click on one of them, you can also see all the details that go into it in terms of a changelog. And so basically here you can see the different features, the fixes and everything, linking

00:35 also the authors that contributed to this release. And you can also have the source code as a zip file that you can download here. So this is what is meant when we talk about GitHub releases. Now in our setup, we just use a workspace level changelog for now, so we don't have any GitHub releases enabled.

00:53 But we can do so by going to the NXJSON and setting the GitHub release there. Now this is mostly around changelog generation. And so we have to adjust here the changelog option. And in there you have the ability to customize the workspace changelog or the product level changelog.

01:12 Now for this one here, since we have a workspace level changelog, let's go with that option. And so I'm opening here the workspace changelog. And then in here we can say create release and specify here GitHub. And so this will now push the changelog and as well as the source code also to our GitHub repo.

01:31 Now usually what you want to do in that case is potentially also to disable the changelog generation in terms of a local file. And so we can disable this to have to be false, which means here this local changelog would not be generated in addition to the GitHub release. And I'm removing that because I'm fine having both of them and we already have it since

01:51 we have an existing repo and just playing around with all of these options. So let's keep it like this for now. Okay, let's commit that. And in my Git history, I previously already added here a feature buttons so we can release a new version. Now again, let me spin up the local Verasha registry so we can actually have this release.

02:10 And then we just run our release script. Let us compile our projects beforehand and then to go and run the versioning, it increments to 1.6.0, pushes to GitHub. You can see here there's now a creating release GitHub release entry since we added that.

02:29 And now it also pushes to our local registry. So if you go now to my GitHub repo where we pushed up the source code, you see here there is the new release that is being pushed up, which is just now. And if I click here, I'm coming here to the releases tab, I see version 1.6.0 got published, who published it? It was me.

02:46 And we have here the same as the changelog that got generated locally. And also the thank you to the author, which in this case, just me, fortunately just myself working on his repo. Which is also linked, which is nice again, because the contributors that potentially helped you push out this release or contribute to this release in general, get a nice notification and recognition of their efforts.