feat: Add publish workflows for npm packages

[amands98]

Implemented the publishing workflow for npm packages using the pascalgn/npm-publish-action.

https://github.com/marketplace/actions/publish-to-npm

Requirements ->
1.) Access token and NPM_TOKEN

How to use ->
Simply push a commit with the name 'Release v*.*'; this action will automatically create the tag and publish the workflow to the npm registry.

Summary by CodeRabbit

• New Features
  • Introduced an automated workflow for publishing the Node.js package to npm upon version tagging in the master branch. This enhances the deployment process and ensures timely updates to users.

[coderabbitai]

Walkthrough

A new GitHub Actions workflow named release.yml has been introduced to automate the publishing of a Node.js package to npm. Triggered by version tags on the master branch, this workflow streamlines the release process, ensuring that updates are automatically deployed with the appropriate versioning. It utilizes secure authentication and manages the publishing through Yarn, enhancing both efficiency and reliability in package management.

Changes

Files	Change Summary
.github/workflows/release.yml	Introduced a new workflow npm-publish to automate npm package publishing on version tags.

Poem

In the garden where code does bloom,
A rabbit dances, dispelling gloom.
With every tag, a new version flies,
Publishing joy, oh how it pries!
Yarn in hand, we hop and cheer,
Automating releases, year after year! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f01f947 and fe64e37.

Files selected for processing (1)

• .github/workflows/release.yml (1 hunks)

Additional comments not posted (5)

.github/workflows/release.yml (5)

1-5: LGTM! Workflow name and trigger event are correctly defined.

The workflow is named npm-publish and is triggered by a push to the master branch.

---

6-9: LGTM! Job name and runner are correctly defined.

The job is named npm-publish and runs on ubuntu-latest.

---

10-12: LGTM! Checkout step is correctly defined.

The repository is checked out using the actions/checkout@v4 action.

---

13-22: LGTM! Publish step is correctly defined.

The pascalgn/[email protected] action is used with appropriate parameters to tag and publish the package.

---

23-25: LGTM! Environment variables are correctly defined and securely referenced.

The GITHUB_TOKEN and NPM_AUTH_TOKEN are securely referenced from secrets.

[piotr-smietana-kaseya]

@Vad1mo Can you take a quick look?