Automate Lumberjack releases

Question

Automate Lumberjack releases

NachoVazquez opened this issue 2 years ago · comments

Nacho Vazquez commented 2 years ago

The Problem

Currently, the release of the new Lumberjack version is a manual and tedious task.

The Goal

Automate the release of new versions using GH Actions.

vimal patel · Answer 1 · Mon Mar 14 2022 00:45:19 GMT+0800 (China Standard Time)

@NachoVazquez I did the same thing in one of my angular package. Here is the link:-
https://github.com/patelvimal/ng-vim-devtools/blob/master/.github/workflows/npm-publish.yml

Whenever I publish using Github then this action gets triggered and will publish the package in npm.

Ajit Panigrahi · Answer 2 · Sat Jul 15 2023 05:30:27 GMT+0800 (China Standard Time)

@NachoVazquez There's a new package to set all this up automatically for Nx repos: Nx-release by @kreuzerk

I recently set this up for my own project, and the steps are very simple to follow. Here's my commit for what you get after setting it up: ajitzero/ng-auto-animate@ad28be4

Here are the CLI commands to run to set this up:

npm i -D nx-release
npx nx g nx-release:configure

You will need to create a GitHub Access token and an NPM access token for this repository. And that's it!

Nacho Vazquez · Answer 3 · Sat Jul 15 2023 05:35:41 GMT+0800 (China Standard Time)

Hi @ajitzero this is actually already addressed. I forgot to update the ticket. We are using https://github.com/jscutlery/semver. That said we have faced some issues with it.

I will be happy to accept a PR with the migration if you are interested.

In the meantime I will take a look at this package.

Thank you!

Ajit Panigrahi · Answer 4 · Sat Jul 15 2023 05:37:19 GMT+0800 (China Standard Time)

I updated my comment above with more details. Please read again if it's at all needed, but if the current setup works fine then I don't think we should migrate anything.

Nacho Vazquez · Answer 5 · Sat Jul 15 2023 20:24:44 GMT+0800 (China Standard Time)

From what I see, we have all this covered by the package I mentioned, we were having some issues with permissions, but the link you provided gave me a few ideas about how to fix it. Thanks for sharing!

I'm going to close this issue since it is already addressed. If you think we should change something in the current workflow, feel free to create a new issue :)