Create CI/CD pipeline to automatically publish packages for every update in `release` branch.

[Ashrockzzz2003]

Right now, we're manually publishing updates to our npm package from the release branch.
We've to create a pipeline to automate this.

• Add CI. #55
• Add CD pipeline. #71

[venkxycodes]

Hey, I can take this up. Need some help wrt the existing npm auth details and stuff..

[Abhinav-ark]

Hey, I can take this up. Need some help wrt the existing npm auth details and stuff..

Sure, We'll set Repository Secrets in the name you want us to.

[Ashrockzzz2003]

This might be a useful resource.
https://docs.github.com/en/actions/use-cases-and-examples/publishing-packages/publishing-nodejs-packages

[venkxycodes]

Thanks Ashwin and Abhinav for the response. How do you guys use the release branch? As in whether you directly push your commits to the release branch or you only merge feature branch commits to the release branch? What is the standard that you follow here?

[Ashrockzzz2003]

So far, it has only been features.

Anything first gets merged to main. After testing it we migrate changes to release, then create the release.
The reason we do this is, the package.json is different for dev and prod.