chore: add release-please workflow

[angelxmoreno]

Summary by CodeRabbit

• Chores
  • Implemented automated npm publishing via GitHub Actions on updates to the main branch when a release is created.
  • No changes to features, APIs, or runtime behavior; improves release consistency and speed.
  • Streamlines versioning and publication of the package, reducing manual steps and potential errors.
  • End users do not need to take any action.

[coderabbitai]

Warning

Rate limit exceeded

@angelxmoreno has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 12 minutes and 1 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 02cbce9 and 4c6b433.

📒 Files selected for processing (2)

• .coderabbit.yaml (2 hunks)
• .github/workflows/release.yml (1 hunks)

Walkthrough

Introduces a GitHub Actions workflow (.github/workflows/release.yml) to automate npm releases on pushes to main. It runs Release Please for a Node package and, when a release is created, sets up Node.js 20 and publishes to npm using the NPM_TOKEN secret.

Changes

Cohort / File(s)	Summary of changes
CI/CD - Release Workflow .github/workflows/release.yml	Adds a GitHub Actions workflow that triggers on push to main, runs Release Please for a Node package (axios-cache-interceptor-keyv), and conditionally sets up Node 20 to publish to npm using NPM_TOKEN when a release is created.

Sequence Diagram(s)

sequenceDiagram
    autonumber
    actor Dev as Developer
    participant GH as GitHub Actions
    participant RP as Release Please
    participant Node as Node Setup (v20)
    participant NPM as npm Registry

    Dev->>GH: Push to main
    GH->>RP: Run Release Please (node package)
    alt Release created
        RP-->>GH: Release artifacts created
        GH->>Node: Setup Node.js 20
        GH->>NPM: npm publish (auth: NPM_TOKEN)
        NPM-->>GH: Publish result
    else No release
        RP-->>GH: No new release
        GH-->>Dev: Workflow completes without publish
    end

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I thump my paw—release day cheer,
A workflow hops when mains draw near.
Tags appear, then Node takes flight,
NPM doors swing wide and bright.
With tokens tucked, I ship with glee—
Carrots for CI, a clean v1.* spree. 🥕🚀

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/release-please

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
  • 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.
• 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.