fix: npm token env var

[rodrigopavezi]

Fixes #29

Changes:

• Change the way the npm token is set based on this documentation

Summary by CodeRabbit

• New Features

  • Simplified authentication process for npm publishing by using an environment variable instead of a configuration file.

• Bug Fixes

  • Enhanced security by eliminating the creation of a potentially sensitive .npmrc file.

• Refactor

  • Standardized string formatting for improved consistency and readability in the workflow configuration.

[coderabbitai]

Walkthrough

The pull request modifies the .github/workflows/npm-publish.yaml file, primarily focusing on the npm package publishing process. It replaces the previous method of setting the npm authentication token through a shell command that created a .npmrc file, with a more secure approach of using an environment variable. Additionally, the formatting of strings has been standardized to enhance consistency throughout the workflow configuration.

Changes

File	Change Summary
.github/workflows/npm-publish.yaml	- Changed npm authentication from .npmrc file setup to using environment variable NODE_AUTH_TOKEN. - Standardized string formatting from double quotes to single quotes.

Assessment against linked issues

Objective	Addressed	Explanation
Modify npm authentication process (undefined)	✅
Standardize string formatting (undefined)	✅

Possibly related issues

• None

Possibly related PRs

• fix: publish #86: This PR also modifies the npm publishing workflow, which is relevant to the changes in this PR.
• chore: call npm whoami and npm config get registry during publish #89: This PR adds verification steps related to npm user and registry settings, aligning with the overall npm publishing process addressed in this PR.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between f95de9b and 1fa3692.

Files selected for processing (1)

• .github/workflows/npm-publish.yaml (3 hunks)

Additional comments not posted (3)

.github/workflows/npm-publish.yaml (3)

17-19: LGTM!

The change from double quotes to single quotes for the package names is a good formatting adjustment for consistency across the configuration. It does not affect the functionality of the workflow.

---

27-28: LGTM!

The change from double quotes to single quotes for the Node.js version is a good formatting adjustment for consistency across the configuration. It does not affect the functionality of the workflow.

---

48-49: Great improvement in simplifying the authentication process and enhancing security! 👍

The change to pass the npm authentication token as an environment variable NODE_AUTH_TOKEN directly to the npm publish command, instead of creating a .npmrc file, has several benefits:

1. It simplifies the authentication process by avoiding the need to create a separate file in the environment.
2. It enhances security by not storing the sensitive token in a file that could potentially be accessed or leaked.
3. It aligns with the best practices for securely managing and using npm tokens during the package publishing process.

Overall, this change improves the workflow's security and maintainability while preserving its functionality.

---

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 using 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.

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.

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.

[MantisClone]

Sure let's try this. 👍